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

Core CAPI CRDs not deployed on unsupported platforms even when explicitly needed by other operators

    XMLWordPrintable

Details

    • No
    • CLOUD Sprint 249
    • 1
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      Core CAPI CRDs not deployed on unsupported platforms even when explicitly needed by other operators.

An example of this is on VSphere clusters. CAPI is not yet supported on VSphere clusters, but the CAPI IPAM CRDs, are needed by other operators than the usual consumer, cluster-capi-operator and the CAPI controllers.

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

      How reproducible:

          Launch a techpreview cluster for an unsupported platform (e.g. vsphere/azure). Check that the Core CAPI CRDs are not present.

      Steps to Reproduce:

          $ oc get crds | grep cluster.x-k8s.io

      Actual results:

          Core CAPI CRDs are not present (only the metal ones)

      Expected results:

          Core CAPI CRDs should be present

      Additional info:

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-29515 [release-4.15] Core CAPI CRDs not deployed on unsupported platforms even when explicitly needed by other operators

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-29515 [release-4.15] Core CAPI CRDs not deployed on unsupported platforms even when explicitly needed by other operators

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/cluster-api#195: OCPBUGS-29476: openshift: generate separate manifest for core CAPI CRDs

          GitHub openshift/cluster-capi-operator#159: OCPBUGS-29476: manifests-gen: store core capi crds also in their own manifest

          Web Link RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update

          Activity

            People

              ddonati@redhat.com Damiano Donati
              ddonati@redhat.com Damiano Donati
              Milind Yadav Milind Yadav
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: