Description:

The output of oc describe infraenv shows inconsistent formatting of the nmstateConfigLabelSelector labels compared to the output of oc get infraenv -o yaml. This inconsistency affects the key-value pairs within the labels, altering their representation.  
 
Steps to Reproduce:

1. Create an InfraEnv resource.

2. Retrieve the YAML of the InfraEnv using

$ oc get infraenv <your_infraenv_name> -o yaml

Observe the nmStateConfigLabelSelector section. For example:

nmStateConfigLabelSelector:
  matchLabels:
    nmstate-label: nodepool

3. Describe the same InfraEnv using:

oc describe infraenv <your_infraenv_name>

4. Observe the Nm State Config Label Selector section.  

Nm State Config Label Selector:
    Match Labels:
      Nmstate - Label:  nodepool ----> Label
 

Actual Results:

The label nmstate-label: nodepool is displayed as Nmstate - Label: nodepool in the oc describe infraenv output. The key "nmstate-label" is changed to "Nmstate - Label".

Nm State Config Label Selector:
  Match Labels:
    Nmstate - Label:   nodepool 

Expected Results:

The formatting of the labels within the Nm State Config Label Selector section in the oc describe infraenv output should consistently match the format used in the oc get infraenv -o yaml output. In this case, it should be displayed as:

Nm State Config Label Selector:
  Match Labels:
    nmstate-label: nodepool 

Impact:
This inconsistency can lead to confusion and potential errors when users try to use or automate based on the oc describe output. Accurate and consistent representation of labels is crucial for reliable configuration management.

Reason for Enhancement (RFE):

To improve user experience and ensure consistency, the oc describe infraenv output should accurately reflect the label key-value pairs as they are represented in the YAML output.  
 
This version incorporates the specific details and examples from the document, making the RFE more precise and compelling.