Support adding owner references to generated secrets and config maps

[jchanam]

Eschewed features

• This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

What would you like to have added?

The possibility of adding an owner reference when generating a secret or configmap

Why is this needed?

Some generated secrets or configmaps lifecycle are coupled to another resource. For example, we can create a job to be run together with a secret. When that job is completed and removed (thanks to a TTL), the secret should be gone to as it's no longer needed.

Can you accomplish the motivating task without this feature, and if so, how?

The only way would be a custom mutating webhook, reading for example an annotation and creating the owner reference. This way is extremely hacky and complex.

What other solutions have you considered?

Have a cronjob to delete old secrets that no longer are used.

Anything else we should know?

No response

Feature ownership

• I am interested in contributing this feature myself! 🎉

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.