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

Add a way to get the full cert chain for issued ACME certificates #1524

Closed
jait opened this issue Apr 4, 2019 · 1 comment
Closed

Add a way to get the full cert chain for issued ACME certificates #1524

jait opened this issue Apr 4, 2019 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jait
Copy link

jait commented Apr 4, 2019

Currently, the issued certificate is stored as a secret that has only the (leaf) certificate and the private key. At least Let's encrypt (possibly all ACME providers?) provides the full cert chain when using certbot. Some applications do want the full cert chain instead of just the leaf certificate, so it would be good if cert-manager would allow this too.

Describe the solution you'd like
One possible solution would be to specify the chain secret name in the Certificate manifest, e.g. fullChainSecretName: my-full-chain, which would be similar to how secretName works now.

Environment details (if applicable):

  • Kubernetes version (e.g. v1.10.2): k3s (v1.13.4-k3s.1)
  • Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): bare metal
  • cert-manager version (e.g. v0.4.0): 0.7.0
  • Install method (e.g. helm or static manifests): static manifest

/kind feature

@jetstack-bot jetstack-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 4, 2019
@jait
Copy link
Author

jait commented Apr 4, 2019

Oops. Nevermind, the full chain is there in the tls.crt file of the secret.

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.
Projects
None yet
Development

No branches or pull requests

2 participants