-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
fix: Allow to pass Kubernetes configuration overrides #5906
Conversation
This allows to override the Kubernetes configuration used to set up the Port Forward. Closes [ISSUE 5905] Signed-off-by: Raphaël Pinson <raphael.pinson@camptocamp.com>
Not sure why the caching step is failing 🤔 |
Seems like a hiccup with GitHub actions to me. I'll re-run the CI. |
Codecov Report
@@ Coverage Diff @@
## master #5906 +/- ##
==========================================
- Coverage 40.89% 40.88% -0.01%
==========================================
Files 147 147
Lines 19633 19634 +1
==========================================
Hits 8028 8028
- Misses 10500 10501 +1
Partials 1105 1105
Continue to review full report at Codecov.
|
Could you please help me with an example @raphink ? |
@sbose78 certainly. In https://github.com/hashicorp/terraform-provider-kubernetes/blob/main/kubernetes/provider.go for example, the code instantiates a clientcmd.ConfigOverrides{} and passes various fields to it based on the Terraform provider parameters. Then they pass the overrides to the client. The idea is to do the same for the ArgoCD provider, by allowing to pass Kubernetes parameters to the provider and pass them in the overrides. This way, users of the provider (and potentially other users of the API client) will be able to specify a cluster and its credentials dynamically. In the context of Terraform, this is useful as we might create the Kubernetes cluster with Terraform, and then pass the generated cluster parameters dynamically to ArgoCD in the same run. This is what we do in our DevOps Stack project, where the At the moment, we need to use a hack to dump the Kube config in a temporary file. Use the ArgoCD Terraform provider would save us from this hack, but we need a way to dynamically pass the cluster credentials to it, in the same Terraform run. Hence this PR. |
Any news on this? Is there any change I need to make? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for providing the link to the workaround that you are using. So the PR allows using Kubernetes overrides by argocd
CLI when port forwarding is used.
LGTM. thank you!
* 4f9c500 (upstream/master) docs: k8s version in Ingress Configuration documentation (argoproj#5727) * 7c88ac8 feat: Allow to pass Kubernetes configuration overrides (argoproj#5906) * 834a5fa chore: Change grammar in high_availability.md (argoproj#5964) * 2a2b81f fix: Improvements to mobile UI (argoproj#5965) * f06fc0d feat: allow per-version kustomize options (argoproj#5967) * 92c7ca0 chore: make argocd gitpod friendly (argoproj#5973) * 1bc3348 Upgrade gitops-engine (argoproj#5972) * a686f12 fix: run dex as nonroot (argoproj#5815) * ed5c5b6 chore: Update go-git to v5 (argoproj#5520) * ac3d4cc fix: correct package name in Makefile (argoproj#5960) * 24b2cac chore: fix incorrect image name in 'publish' CI job (argoproj#5956) * b37eee1 chore: fix invalid IMAGE_NAMESPACE in image 'publish' CI job (argoproj#5953) * dc4eaff chore: Remove specification of user id for the Redis workload (argoproj#5863) * 8eeb9a0 chore: use clusterrolebinding v1 (argoproj#5939) * 7945286 docs: clarify that the certificate must be in PEM format (argoproj#5946) * de522bf chore: migrate argocd dev images to ghcr.io (argoproj#5948) * 0a53fb1 chore(deps): bump y18n from 4.0.0 to 4.0.1 in /ui (argoproj#5919) * ae49b45 chore: Upgrade Go module to v2 (argoproj#5931) * a2ebe15 add user (argoproj#5938) * 7f5a23d Update USERS.md (argoproj#5835) * 24218b4 docs: Propose an enhancement proposal process (argoproj#5771)
This allows to override the Kubernetes configuration used to set up the Port Forward. Closes [ISSUE 5905] Signed-off-by: Raphaël Pinson <raphael.pinson@camptocamp.com>
This allows to override the Kubernetes configuration used to set up the
Port Forward.
Signed-off-by: Raphaël Pinson raphael.pinson@camptocamp.com
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist: