Anatomy of an Infrastructure node

Understand the infrastructure node attributes.

Infrastructure nodes for use with Fusion Data Foundation have a few attributes. The infra node-role label is required to ensure the node does not consume Red Hat OpenShift Container Platform entitlements. The infra node-role label is responsible for ensuring only Fusion Data Foundation entitlements are necessary for the nodes running Fusion Data Foundation.

Labeled with node-role.kubernetes.io/infra

Adding an Fusion Data Foundation taint with a NoSchedule effect is also required so that the infra node will only schedule Fusion Data Foundation resources.

Tainted with node.ocs.openshift.io/storage="true"

The label identifies the Red Hat OpenShift Container Platform node as an infra node so that Red Hat OpenShift Container Platform subscription cost is not applied. The taint prevents non Fusion Data Foundation resources to be scheduled on the tainted nodes.

Note: Adding storage taint on nodes might require toleration handling for the other daemonset pods such as openshift-dns daemonset. For information about how to manage the tolerations, see [RHOCP 4.x] openshift-dns daemonset doesn't include toleration to run on nodes with taints on the Red Hat Customer Portal.

Example of the taint and labels required on infrastructure node that will be used to run Fusion Data Foundation services:

    spec:
      taints:
      - effect: NoSchedule
        key: node.ocs.openshift.io/storage
        value: "true"
      metadata:
        creationTimestamp: null
        labels:
          node-role.kubernetes.io/worker: ""
          node-role.kubernetes.io/infra: ""
          cluster.ocs.openshift.io/openshift-storage: ""