Propagate labels from profile custom resource to controller-generated namespace

[droctothorpe]

/kind feature

Why you need this feature:
We use the profile operator directly instead of pathing through the UI. We want end user namespaces to have specific labels (that identify various things about the user). This code lets administrators set global namespace labels, but there's no mechanism to pass custom-resource-specific, non-global labels.

Describe the solution you'd like:
The simplest way to implement this is to just propagate labels from the profile custom resource to the corresponding namespace. It's a one line change to the controller logic.

Anything else you would like to add:
I'll submit a PR momentarily.

[andreyvelich]

/transfer dashboard

[google-oss-prow]

@droctothorpe: The label(s) kind/feature cannot be applied, because the repository doesn't have them.

In response to this:

/kind feature

Why you need this feature:
We use the profile operator directly instead of pathing through the UI. We want end user namespaces to have specific labels (that identify various things about the user). This code lets administrators set global namespace labels, but there's no mechanism to pass custom-resource-specific, non-global labels.

Describe the solution you'd like:
The simplest way to implement this is to just propagate labels from the profile custom resource to the corresponding namespace. It's a one line change to the controller logic.

Anything else you would like to add:
I'll submit a PR momentarily.

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.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[juliusvonkohout]

/lifecycle frozen