-
Notifications
You must be signed in to change notification settings - Fork 91
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
Error: Failed to init clients #231
Comments
I haven't used the provider alongside a
How have you gone about doing these checks? In particular, which parameters are you passing to the |
Hello there, Was having the same issue on an openshift cluster with their argo installation (which is named openshift-gitops), got another error when adding the port_forward options: Error: Failed to init clients
│
│ with argocd_project.argo_project,
│ on providers.tf line 106, in resource "argocd_project" "argo_project":
│ 106: resource "argocd_project" "argo_project" {
│ cannot find pod with selector:
│ [app.kubernetes.io/name=argocd-server] I think this is related to: argoproj/argo-cd#10200 (which I created) If it's related to the issue I mentionned, a pull request is still waiting for the merge here: argoproj/argo-cd#11297 EDIT: |
Sorry @onematchfox I will answer from memory, I will come back when have more precise data. I am using argocd loadbalancer option(not port forward or ingress) .
Also
I will say also tried with a ip address:port Thanks |
Hi @Diliz I am indeed using a argocd default installation from this repo , I will try port forward option ASAP |
@mikzuit, the provider should be configured using the same parameters as what works when you use provider "argocd" {
server_addr = "IP_ADDRESS"
username = "admin"
password = "password"
insecure = true
grpc_web = true
} |
@Diliz, I'm afraid the provider uses the Edit: It might also be worth asking if there is a reason you cannot expose the ArgoCD server. If you do so, then, as per my comment above, there is no need to use port-forwarding to connect to it. You can simply configure the provider to connect to whatever DNS/port the server is exposed on. |
Hi @oboukili could this be related to sh scripts, LF CRLF or argocd provider authentication?
Setup:
Terraform : 1.0.6
Argocd terraform provider: 4.3.0
Config files:
I execute this script in order to add my agent ssh then use it in private repos.
ssh-init.sh
main.tf
Regular output:
TF_LOG=Debug output:
Questions:
Failed to init client: kubernetes configuration invalid #134
I have used the env variables KUBE_CONFIG_PATH , KUBECONFIG as suggested there.
Other things I tried:
UPDATE: (solution)
This is the minimun login with cli (--plaintext) to avoid TLS error warning message):
Agocd providers does have that option as
plain_text
which SOLVES the problem.Thanks for the help @onematchfox @Diliz
Thanks
The text was updated successfully, but these errors were encountered: