Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-35752

OpenShift Installer on AWS: EKS CAPA is enabled by default

XMLWordPrintable

    • No
    • Installer Sprint 256
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when installing a cluster on {aws-short}, Elastic Kubernetes Service (EKS) messages could appear in the installation logs even when EKS was meant to be disabled. With this update, EKS log messages have been disabled. (link:https://issues.redhat.com/browse/OCPBUGS-35752[*OCPBUGS-35752*])
      Show
      * Previously, when installing a cluster on {aws-short}, Elastic Kubernetes Service (EKS) messages could appear in the installation logs even when EKS was meant to be disabled. With this update, EKS log messages have been disabled. (link: https://issues.redhat.com/browse/OCPBUGS-35752 [* OCPBUGS-35752 *])
    • Bug Fix
    • Done

      Description of problem:

      When installing a fresh 4.16-rc.5 on AWS, the following logs are shown:

time="2024-06-18T16:47:23+02:00" level=debug msg="I0618 16:47:23.596147    4921 logger.go:75] \"enabling EKS controllers and webhooks\" logger=\"setup\""
time="2024-06-18T16:47:23+02:00" level=debug msg="I0618 16:47:23.596154    4921 logger.go:81] \"EKS IAM role creation\" logger=\"setup\" enabled=false"
time="2024-06-18T16:47:23+02:00" level=debug msg="I0618 16:47:23.596159    4921 logger.go:81] \"EKS IAM additional roles\" logger=\"setup\" enabled=false"
time="2024-06-18T16:47:23+02:00" level=debug msg="I0618 16:47:23.596164    4921 logger.go:81] \"enabling EKS control plane controller\" logger=\"setup\""
time="2024-06-18T16:47:23+02:00" level=debug msg="I0618 16:47:23.596184    4921 logger.go:81] \"enabling EKS bootstrap controller\" logger=\"setup\""
time="2024-06-18T16:47:23+02:00" level=debug msg="I0618 16:47:23.596198    4921 logger.go:81] \"enabling EKS managed cluster controller\" logger=\"setup\""
time="2024-06-18T16:47:23+02:00" level=debug msg="I0618 16:47:23.596215    4921 logger.go:81] \"enabling EKS managed machine pool controller\" logger=\"setup\""

That is somehow strange and may have side effects. It seems the EKS CAPA is enabled by default (see additional info)

      Version-Release number of selected component (if applicable):

      4.16-rc.5

      How reproducible:

      Always

      Steps to Reproduce:

      1. Install an cluster (even an SNO works) on AWS using IPI

      Actual results:

      EKS feature enabled

      Expected results:

      EKS feature not enabled

      Additional info:

      https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/feature/feature.go#L99

              rdossant Rafael Fonseca dos Santos
              rgordill1@redhat.com Ramon Gordillo Gutierrez
              Yunfei Jiang Yunfei Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: