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 cert-manager as an UpstreamAuthority #1796

Closed
JoshVanL opened this issue Aug 18, 2020 · 1 comment · Fixed by #2274
Closed

Add cert-manager as an UpstreamAuthority #1796

JoshVanL opened this issue Aug 18, 2020 · 1 comment · Fixed by #2274

Comments

@JoshVanL
Copy link
Contributor

This is a feature request for adding cert-manager as an UpstreamAuthority to Spire.

This would enable Spire certificates to be signed by cert-manager issuers core and external.

Certificate requests can be created by creating cert-manager CertificateRequest resources, that are signed by the configured issuer on spire:

  • issuer-name
  • issuer-kind
  • issuer-group

Happy to put together a PR if this is something we want to move forward with!

@evan2645
Copy link
Member

Hi @JoshVanL! Sorry for the delay here,

I'm afraid I'm only passingly familiar with cert-manager. I am reading up on it a little bit to see exactly the capabilities, and what sort of integrations make sense. So please forgive my questions here :)

SPIRE UpstreamAuthority attempts to get an intermediate CA cut. When the plugin is loaded, SPIRE Server sends a CSR for this intermediate on boot (assuming one is not cached), and every time the SPIRE authoritative keys rotate. Can cert-manager vend intermediate CA certs?

I'm also curious to learn more about how we might authenticate to an upstream cert-manager, but I think my previous question is most relevant. If the answer to the first question is "yes", I don't see why we wouldn't want an integration! Would you be willing to maintain it long term?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants