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

additional ca-bundle source options: pvc, url #379

Open
lknite opened this issue Jul 9, 2024 · 2 comments
Open

additional ca-bundle source options: pvc, url #379

lknite opened this issue Jul 9, 2024 · 2 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@lknite
Copy link

lknite commented Jul 9, 2024

My source ca-bundle location is via a url, specifically vault provides a url to access its public ca-bundle which includes root and intermediate. (e.g. https://vault.vc-prod.home.net:8200/v1/prod-intermediate-ca/ca_chain)

I can access this via kubernetes by using an initContainer & pvc:

  • mount the pvc as a volume with initContainer
  • inside the initContainer use curl to pull the latest ca-bundle, save to pvc mount location

Now I just need to provide this location to trust-manager in the ca-bundle resource.

  • either by providing the pvc & location in the usual way
  • OR, we could get around the initContainer & pvc, if it were possible to provide a url location in the Bundle resource
@lknite lknite changed the title Additional ca-bundle source options: pvc, url additional ca-bundle source options: pvc, url Jul 9, 2024
@cert-manager-bot
Copy link
Contributor

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.
/lifecycle stale

@cert-manager-prow cert-manager-prow bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 6, 2024
@cert-manager-bot
Copy link
Contributor

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.
/lifecycle rotten
/remove-lifecycle stale

@cert-manager-prow cert-manager-prow 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 Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

2 participants