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

[AWS] Prevent usage of various AWSMachineSpec fields

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • None
    • None
    • None
    • CLOUD Sprint 271, CLOUD Sprint 272, CLOUD Sprint 273, CLOUD Sprint 274, CLOUD Sprint 275, CLOUD Sprint 276

      Background

      CAPA supports a number of fields/features that don't make sense in OpenShift. To prevent issues with general usage and conversion, we should prevent users from leveraging these fields at all.

      A VAP should be introduced to cover AWSMachineTemplate and AWSMachines that prevents the use of the following spec fields

      • spec.ami.eksOptimizedLookupType
      • spec.imageLookupFormat
      • spec.imageLookupOrg
      • spec.imageLookupBaseOS
      • spec.networkInterfaces
      • spec.uncompressedUserData
      • spec.cloudInit
      • spec.privateDNSName
      • spec.ignition.proxy
      • spec.ignition.tls
      • spec.securityGroupOverrides

      Steps

      • Create a VAP and binding in the cluster-api-provider-aws repo that will be added to the transport configmap
      • Prevent the usage of each of the above fields with a unique rule
      • Scope the VAP to only the openshift-cluster-api namespace

      Stakeholders

      • Cluster Infra

      Definition of Done

      • Unsupported fields cannot be used in the openshift-cluster-api namespace
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

              rmanak@redhat.com Radek Manak
              joelspeed Joel Speed
              None
              None
              Huali Liu Huali Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: