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

feat(k8s): extend k8s provider to fetch configmap #191

Merged
merged 1 commit into from
Dec 23, 2023

Conversation

bersalazar
Copy link
Contributor

@bersalazar bersalazar commented Dec 22, 2023

The k8s provider now supports fetching values from ConfigMaps.

Covers: #187

The k8s provider now supports fetching values from ConfigMaps.

Signed-off-by: Bernardo Salazar <[email protected]>
@yxxhero yxxhero merged commit 669351c into helmfile:main Dec 23, 2023
3 checks passed
@lucasfcnunes
Copy link
Contributor

@bersalazar, we should've updated the following:

vals/README.md

Lines 727 to 748 in 17fd11a

### Kubernetes
Fetch value from a Kubernetes:
- `ref+k8s://API_VERSION/KIND/NAMESPACE/NAME/KEY[?kubeConfigPath=<path_to_kubeconfig>&kubeContext=<kubernetes context name>]`
Authentication to the Kubernetes cluster is done by referencing the local kubeconfig file.
The path to the kubeconfig can be specified as a URI parameter, read from the `KUBECONFIG` environment variable or the provider will attempt to read `$HOME/.kube/config`.
The Kubernetes context can be specified as a URI parameteter.
Environment variables:
- `KUBECONFIG` contains the path to the Kubeconfig that will be used to fetch the secret.
Examples:
- `ref+k8s://v1/Secret/mynamespace/mysecret/foo`
- `ref+k8s://v1/Secret/mynamespace/mysecret/bar?kubeConfigPath=/home/user/kubeconfig`
- `secretref+k8s://v1/Secret/mynamespace/mysecret/baz`
- `secretref+k8s://v1/Secret/mynamespace/mysecret/baz?kubeContext=minikube`
> NOTE: This provider only supports kind "Secret" in apiVersion "v1" at this time.

Specially the part:

NOTE: This provider only supports kind "Secret" in apiVersion "v1" at this time.

@lucasfcnunes
Copy link
Contributor

Thanks for addressing #191 (comment) on #192

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 this pull request may close these issues.

3 participants