Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-3162

AWS: MAPI to CAPI conversion should not set the ignition version field

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • CLOUD Sprint 277

      Background

      Currently, in the MAPI to CAPI conversion we hard code the ignition version.
      This was a required field until CAPA > v2.9 / OCPCLOUD-2719 was implemented

      After bumping to a supported version, we should stop setting an ignition version during MAPI to CAPI conversion.

      Steps

      • Ensure CAPA was bumped to > 2.9.0
      • Drop version handling (hardcoded to `3.4`)

      Stakeholders

      • Cluster Infra

      Definition of Done

      • Cluster CAPI Operator (CCO) does not set ignition version anymore on AWSMachine's or AWSMachineTemplates
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

              rh-ee-cschlott Christian Schlotter
              rh-ee-cschlott Christian Schlotter
              None
              None
              Huali Liu Huali Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: