Connect argocd to local kube-apiserver
Name and Version
bitnami/argocd-2.12.3
What architecture are you using?
amd64
What steps will reproduce the bug?
K8s 1.29.3 bitnami/argocd-2-12.3 kube-apiserver:1.29.3
I want to connect to local kube-apiserver running in my namespace instead of k8s cluster
Are you using any custom parameters or values?
no
What is the expected behavior?
I want to know how to provide the Kubernetes service URL to the argocd
What do you see instead?
Unable to connect to local k8s service
Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.
If you think that's not the case and want to contribute a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Hi, can I create my own secrets? I see argocd-secrets.yaml file to create secrets but i want to create my own and understand the procedure to create my own. Can someone explain this, please? I see the admin password in the secret is created using the user password provided. Can I not do this?
clearPassword: {{ $password }}
{{- $password = (trimAll "\"" $password) | b64dec }}
## The password needs to be bcrypt hashed
admin.password: {{ (split ":" (htpasswd "" $password))._1 | b64enc }}