-
Notifications
You must be signed in to change notification settings - Fork 289
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
Get all k/v pairs from endpoint #529
Comments
Everything within
If there are commonalities between the solutions then we can investigate feasibility of a shared feature of the driver itself. |
@tam7t I completely understand that perspective. the |
Ah yes, |
/assign |
+1 Looking forward to the detailed design doc so we can discuss some of the nuances this feature may bring. Specifically, today with the With this feature request/proposal, the list of objects is maintained outside of the SPC CR via |
Perhaps not directly related, but I wonder if inspiration could be drawn from the Vault Injector Sidecar's options, such as in the use of template files to extract and format a vault secret into a format that most applications can use natively (such as a .env file or a bash script with exported env vars). https://www.vaultproject.io/docs/platform/k8s/injector#secret-templates |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
This feature would reduce security concerns massively and will be widely celebrated! |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This really shouldn’t be a stale issue. |
/remove-lifecycle stale |
We're seeing strong traction for this request in the AWS provider (issue) |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Has it been decided if this is entirely up to the providers to implement, or if changes are needed in this repo first? Provider feature requests:
|
Hi, is there any update regarding this suggested feature? |
Is there any update on this issue? It would really help for deployments made using reutilizable code to create common K8s entities (namespaces, secrets stores, etc). The workaround is currently a bit hacky (at least using AWS driver) |
Would like to bump this issue as it would be a really great feature to have |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Bump. This would be epic. |
+1 |
+10 |
Motivation
Some applications require a significant amount of configuration that is sensitive. This becomes extremely tedious and adds redundancy and toil where it could be reduced using the same functionality that
envFrom
uses in kubernetes core as well as established solutions like external-secretsDescribe the solution you'd like
2 Separate requests.
A practical example with only 5 k/v pairs currently looks like:
When all you should really need is
The text was updated successfully, but these errors were encountered: