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

[DOCS] node-role.kubernetes.io/control-plane is not added automatically in existing OpenShift Container Platform - Cluster

    XMLWordPrintable

Details

    • Important
    • No
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

    Description

      Description of problem:

      node-role.kubernetes.io/control-plane is a new label introduced for the OpenShift Container Platform 4 - Control-Plane Node(s) as per https://kubernetes.io/docs/reference/labels-annotations-taints/#node-role-kubernetes-io-control-plane.

While it's automatically added for newly installed OpenShift Container Platform 4 - Cluster and newly created OpenShift Container Platform 4 - Control-Plane Node(s), it's not enforced or created for existing OpenShift Container Platform 4 - Cluster respectively existing OpenShift Container Platform 4 - Control-Plane Node(s).

This can be confusing for customers having long running OpenShift Container Platform 4 - Cluster and newly created OpenShift Container Platform 4 - Cluster as the default set of labels applied to the OpenShift Container Platform 4 - Control-Plane Node(s) are not the same.

It's therefore requested to document the reasoning behind this and to recommend to customers to manually add  node-role.kubernetes.io/control-plane to their existing OpenShift Container Platform 4 - Cluster to achieve consistency between newly created OpenShift Container Platform 4 - Cluster and long running OpenShift Container Platform 4 - Cluster.

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

      OpenShift Container Platform 4.11, 4.12 and 4.13

      How reproducible:

      Always

      Steps to Reproduce:

      1. See problem description

      Actual results:

      Inconsistency that is per design but not documented that may raise question and support volume specifically when troubleshooting.

      Expected results:

      Outline node-role.kubernetes.io difference between newly installed OpenShift Container Platform 4 - Cluster and long running OpenShift Container Platform 4 - Cluster and also provide details how long running OpenShift Container Platform 4 - Clusters can be label to have node-role.kubernetes.io/control-plane set as well and therefore comply with upstream kubernetes and newly installed OpenShift Container Platform 4 - Cluster

      Additional info:

      https://issues.redhat.com/browse/OCPNODE-709

      Attachments

        Issue Links

          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OCPNODE-709 Control-plane nodes need the node-role.kubernetes.io/control-plane label

          • 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

          Web Link Inconsistency of node-role.kubernetes.io between newly created vs. long running OpenShift Container Platform 4 - Cluster

          Activity

            People

              rhn-support-stk Subhashini T K
              rhn-support-sreber Simon Reber
              Sunil Choudhary Sunil Choudhary
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: