Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically add annotations to TLS secrets #933

Closed
jjtroberts opened this issue Oct 4, 2018 · 7 comments
Closed

Automatically add annotations to TLS secrets #933

jjtroberts opened this issue Oct 4, 2018 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@jjtroberts
Copy link

FEATURE REQUEST

WHAT
I would like cert-manager to automatically apply annotations from either a given list in values.yaml, or copy from annotations applied to the certificate resource itself.

WHY
I use [kubed|https://github.com/appscode/kubed] to propagate TLS secrets across namespaces and clusters. kubed uses the following annotation to accomplish this: kubed.appscode.com/sync="" but can also target specific labels.

HOW
Right now I have cert-manager creating Let's Encrypt wildcard TLS certs in the kubed namespace, but I still must manually apply annotations to each TLS secret in order for those updated secrets to be propagated across the cluster. I have not yet had a renewal so I cannot say whether or not the annotations would need to be reapplied after each renewal.

I realize I could add a CronJob to automate the applying of these annotations, however, having this built-in would mean one less service to manage in every cluster.

/kind feature

@jetstack-bot jetstack-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 4, 2018
@retest-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

@jetstack-bot jetstack-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2019
@retest-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

@jetstack-bot jetstack-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 1, 2019
@munnerz
Copy link
Member

munnerz commented Feb 7, 2019

Closing in favour of #977

@munnerz munnerz closed this as completed Feb 7, 2019
@dioguerra
Copy link

It appears that #977 does not solve this issue, but issues labels only instead, Am i wrong?

@jkremser
Copy link

@dioguerra I am also on it and found this:

λ k explain certificate.spec.secretTemplate.annotations
KIND:     Certificate
VERSION:  cert-manager.io/v1

FIELD:    annotations <map[string]string>

DESCRIPTION:
     Annotations is a key value map to be copied to the target Kubernetes
     Secret.

@pjamenaja
Copy link

Not sure if this link can solve the issue?
https://cert-manager.io/docs/tutorials/syncing-secrets-across-namespaces/

@rofreytag
Copy link

I believe this is the right way to apply annotations to secrets generated by cert-manager:

https://cert-manager.io/docs/reference/api-docs/#cert-manager.io/v1.CertificateSecretTemplate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

8 participants