This repository has been archived by the owner on Nov 15, 2022. It is now read-only.
Add support for envFrom for secrets #85
Comments
Closed
pradeepto
added
kind/discussion
priority/low
status/undecided
priority/high
and removed
priority/urgent
priority/low
labels
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jul 24, 2017
This commit allows defining root level secrets, as well as referencing those from the `envFrom` directive, which currently only supports configMaps. Minor refactors have been made in kubernetes.go to handle envFrom behavior for ConfigMaps and Secrets in a more consistent manner. The examples, related READMEs, and the file reference doc have also been modified to reflect the changes being brought upon. fixes kedgeproject#128 fixes kedgeproject#85
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jul 24, 2017
This commit allows defining root level secrets, as well as referencing those from the `envFrom` directive, which currently only supports configMaps. Minor refactors have been made in kubernetes.go to handle envFrom behavior for ConfigMaps and Secrets in a more consistent manner. The examples, related READMEs, and the file reference doc have also been modified to reflect the changes being brought upon. fixes kedgeproject#128 fixes kedgeproject#85
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jul 27, 2017
This commit allows defining root level secrets, as well as referencing those from the `envFrom` directive, which currently only supports configMaps. Minor refactors have been made in kubernetes.go to handle envFrom behavior for ConfigMaps and Secrets in a more consistent manner. The examples, related READMEs, and the file reference doc have also been modified to reflect the changes being brought upon. fixes kedgeproject#128 fixes kedgeproject#85
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jul 31, 2017
This commit allows defining root level secrets, as well as referencing those from the `envFrom` directive, which currently only supports configMaps. Minor refactors have been made in kubernetes.go to handle envFrom behavior for ConfigMaps and Secrets in a more consistent manner. The examples, related READMEs, and the file reference doc have also been modified to reflect the changes being brought upon. fixes kedgeproject#128 fixes kedgeproject#85
concaf
added a commit
to concaf/kedge
that referenced
this issue
Jul 31, 2017
This commit allows defining root level secrets, as well as referencing those from the `envFrom` directive, which currently only supports configMaps. Minor refactors have been made in kubernetes.go to handle envFrom behavior for ConfigMaps and Secrets in a more consistent manner. The examples, related READMEs, and the file reference doc have also been modified to reflect the changes being brought upon. fixes kedgeproject#128 fixes kedgeproject#85
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is secret only, the work to add support for configMap can be tracked in PR #84 and issue #43
Kubernetes 1.6 release added support for envFrom, and example of which can be seen here.
We see there is a pattern in most/a lot of the Kubernetes deployments that all fields from a Secret are exposed inside the containers of a pod, so we can leverage this field.
Since, Kubernetes v1.6 is fairly new, we might need to support this field for now in our tooling, and after a while, we can leverage it directly.
This partially resolves the wildcard discussions in #2.
The text was updated successfully, but these errors were encountered: