Bug 2005843: Label ODF multicluster operator pod based on deployment name

[GowthamShanmugam]

Keep labels of one operator pods always unique from the other
operator pods, So that label based fetching of pods can be more
deterministic.

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2005843

[openshift-ci]

@GowthamShanmugam: This pull request references Bugzilla bug 2005843, which is valid.

No validations were run on this bug

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (ratamir@redhat.com), skipping review request.

In response to this:

Bug 2005843: Label ODF multicluster operator pod based on deployment name

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[GowthamShanmugam]

@sp98 @umangachapagain

I dont know-how this PR #43 is closed, created a new PR with all the changes which we discussed.

[sp98]

/lgtm

[openshift-ci]

@sp98: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[umangachapagain]

No need to make changes manually.

Just add

# Labels to add to all resources and selectors.
commonLabels:
 control-plane: odfmo-controller-manager

here:

odf-multicluster-orchestrator/config/manifests/kustomization.yaml

Line 1 in eef4386

# These resources constitute the fully configured set of manifests

and run make bundle. It will add labels to all generated resources.
Keep it in one commit.

[GowthamShanmugam]

# Labels to add to all resources and selectors.
commonLabels:
 control-plane: odfmo-controller-manager

ack

[umangachapagain]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GowthamShanmugam, umangachapagain

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [umangachapagain]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[umangachapagain]

/cherrypick release-4.9

[openshift-cherrypick-robot]

@umangachapagain: new pull request created: #47

In response to this:

/cherrypick release-4.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.