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

KAS postStart hook doesn't respect hostedcluster.spec.networking.apiServer.port

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 4.21.0
    • 4.20, 4.21
    • HyperShift
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • Approved
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      4.20 hypershift added a postStart hook to KAS which hardcodes 6443 port for it's check: https://github.com/openshift/hypershift/blob/d29713d06741fb622fd0deed29c9c073b5c61495/control-plane-operator/controllers/hostedcontrolplane/v2/assets/kube-apiserver/deployment.yaml#L43C49-L43C53

However there is an option to set a custom apiserver port in `hostedcluster.spec.networking.apiServer.port`: https://github.com/openshift/hypershift/blob/d29713d06741fb622fd0deed29c9c073b5c61495/control-plane-operator/controllers/hostedcontrolplane/v2/kas/deployment.go#L112

If this option is set to anything but the default, the apiserver will fail to come up.

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

      4.20, 4.21

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create 4.20 HostedCluster with hostedcluster.spec.networking.apiServer.port set to 2040 (IBMCloud default)

      Actual results:

      KAS will be stuck PodInitializing

      Expected results:

      KAS comes up fine

      Additional info:

              mate-lajko Máté Lajkó
              zszepesi Zoltan Szepesi
              None
              None
              Yu Li Yu Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: