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

Cluster Install with disabled Ingress capability does not disable Ingress

XMLWordPrintable

    • Critical
    • No
    • Approved
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when installing a cluster, the Ingress capability was enabled even if it was disabled in `install-config.yaml` because it is required. With this update, the installation program fails if the Ingress capability is disabled in `install-config.yaml`. (link:https://issues.redhat.com/browse/OCPBUGS-33794[*OCPBUGS-33794*])
      Show
      * Previously, when installing a cluster, the Ingress capability was enabled even if it was disabled in `install-config.yaml` because it is required. With this update, the installation program fails if the Ingress capability is disabled in `install-config.yaml`. (link: https://issues.redhat.com/browse/OCPBUGS-33794 [* OCPBUGS-33794 *])
    • Bug Fix
    • Done

      Description of problem:

          If I use custom CVO capabilities via the install config, I can create a capability set that disables the Ingress capability.
However, once the cluster boots up, the Ingress capability will always be enabled.
This creates a dissonance between the desired install config and what happens.
It would be better to fail the install at install-config validation to prevent that dissonance.

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

          4.16

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

              alebedev@redhat.com Andrey Lebedev
              joelspeed Joel Speed
              Jinyun Ma Jinyun Ma
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: