Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-3190

Heterogeneous architecture clusters - Operator Hub filtering


    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • OLM Screens
    • HAC Infra OCP - Sprint 226

      This enhancement Introduces support for provisioning and upgrading heterogenous architecture clusters in phases.


      We need to scan through the compute nodes and build a set of supported architectures from those. Each node on the cluster has a label for architecture: e.g. `kuberneties.io/arch:arm64`, `kubernetes.io/arch:amd64` etc. Based on the set of supported architectures console will need to surface only those operators in the Operator Hub, which are supported on our Nodes. Each operator's PackageManifest contains a labels that indicates whats the operator's supported architecture, e.g.  `operatorframework.io/arch.s390x: supported`. An operator can be supported on multiple architectures


      1. Implement logic in the console's backend to read the set of architecture types from console-config.yaml and set it as a SERVER_FLAG.nodeArchitectures (Change similar to https://github.com/openshift/console/commit/39aabe171a2e89ed3757ac2146d252d087fdfd33)
      2. In Operator hub render only operators that are support on any given node, based on the SERVER_FLAG.nodeArchitectures field implemented in CONSOLE-3242.


      OS and arch filtering: https://github.com/openshift/console/blob/2ad4e17d76acbe72171407fc1c66ca4596c8aac4/frontend/packages/operator-lifecycle-manager/src/components/operator-hub/operator-hub-items.tsx#L49-L86


      @jpoulin is good to ask about heterogeneous clusters.

            rhn-engineering-rhamilto Robb Hamilton
            jhadvig@redhat.com Jakub Hadvig
            Xiyun Zhao Xiyun Zhao
            0 Vote for this issue
            7 Start watching this issue