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

Strategic Merge Patch not supported for DNS.spec.servers

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • Rejected
    • NI&D Sprint 278
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      dns.operator.openshift.io custom resource currently doesn't support strategic merge patch for .spec.servers map, as patchMergeKey is not defined. This avoids providing dns forward definitions via argocd and submariner operator in parallel.

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

      4.18

      How reproducible:

      Use SSA to patch dns.operator.openshift.io resource in .spec.servers with different map entries.

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Patches override each other as no patchMergeKey is defined.

      Expected results:

      Maps getting merged together based on name field.

      Additional info:

      Open github issue: https://github.com/openshift/api/issues/2514
Kubernetes docs regards patchMergeKey: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/#merge-individual-elements-of-a-list-of-complex-elements
Link to dns.operator.openshift.io type definition where patchMergeKey is missing: https://github.com/openshift/api/blob/bfcb56b390563c584d132ee0728f6ffc660e8e15/operator/v1/types_dns.go#L55

              rh-ee-alsyed Ali Syed
              sascha.tanke@bdr Sascha Tanke
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: