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 an ability to communicate with Vault via mTLS #2926

Closed
itisevgeny opened this issue May 19, 2020 · 4 comments
Closed

Add an ability to communicate with Vault via mTLS #2926

itisevgeny opened this issue May 19, 2020 · 4 comments
Labels
area/vault Indicates a PR directly modifies the Vault Issuer code 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. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@itisevgeny
Copy link

itisevgeny commented May 19, 2020

Is your feature request related to a problem? Please describe.
Vault server can be configured to request client certificates:
https://www.vaultproject.io/docs/configuration/listener/tcp
(tls_client_ca_file, tls_disable_client_certs)
When Vault is configured in the way above, there is no possibility to properly configure Vault Issuer by using existing CRDs.

Describe the solution you'd like
As a cert-manager user I want to have an ability to provide client certificate for Vault Issuer.

Describe alternatives you've considered
No alternatives when Vault requests client certificates.

Environment details (if applicable):

  • Kubernetes version (e.g. v1.10.2): any
  • Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): any
  • cert-manager version (e.g. v0.4.0): any
  • Install method (e.g. helm or static manifests): any

/kind feature

@jetstack-bot jetstack-bot added the kind/feature Categorizes issue or PR as related to a new feature. label May 19, 2020
@meyskens meyskens added area/vault Indicates a PR directly modifies the Vault Issuer code priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels May 20, 2020
@jetstack-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.
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 Sep 15, 2021
@jetstack-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.
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 Oct 15, 2021
@jetstack-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

@jetstack-bot
Copy link
Contributor

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vault Indicates a PR directly modifies the Vault Issuer code 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. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

3 participants