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

dns-default pod missing "target.workload.openshift.io/management:" annotation

XMLWordPrintable

    • None
    • 3
    • Sprint 226, Sprint 227
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      The default dns-default pod is missing the "target.workload.openshift.io/management:" annotation, and as a
      result when the workload partitioning feature is enabled on SNO, the pod resources will not get mutated and pinned to the reserved cpuset. The fix was to make sure all annotations were handled properly when new annotations were added. Now, annotations that exist prior to reconcilation, are retained after reconciliation.
      Show
      The default dns-default pod is missing the "target.workload.openshift.io/management:" annotation, and as a result when the workload partitioning feature is enabled on SNO, the pod resources will not get mutated and pinned to the reserved cpuset. The fix was to make sure all annotations were handled properly when new annotations were added. Now, annotations that exist prior to reconcilation, are retained after reconciliation.

      This is a clone of issue OCPBUGS-753. The following is the description of the original issue:

      Description of problem:

      The default dns-default pod is missing the "target.workload.openshift.io/management:" annotation. 
      
      As a result when the workload partitioning feature is enabled on SNO, this pod resources will not get mutated and pinned to the reserved cpuset.
      
      This is a regresion from 4.10. Pod spec from 4.10.17
      
      Annotations:
      ...
         resources.workload.openshift.io/dns: {"cpushares": 51}
         resources.workload.openshift.io/kube-rbac-proxy: {"cpushares": 10}
         target.workload.openshift.io/management {"effect":"PreferredDuringScheduling"}
      

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

      4.11.0

      How reproducible:

      100%

      Steps to Reproduce:

      1. Install a SNO and check the annotation
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

       

            cholman@redhat.com Candace Holman
            openshift-crt-jira-prow OpenShift Prow Bot
            Shudi Li Shudi Li
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: