Replies: 1 comment
-
It works after I added SAN for the domain foo in certificate of the cluster foo and set insecure to false. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Im trying to deploy an Application to another cluster (not in-cluster), so I added Secret for cluster (
argocd.argoproj.io/secret-type: cluster
) with certificate as a credential but it does not work.It reports: "cluster 'https://foo.com:6443/' has not been configured".
However, if I use
argocd cluster add foo
, the Application successfully deployed.What is difference? Is it related to the service account (
argocd-manager
) that is created on the cluster foo when the cluster is added using CLI?If so, why need another bearer token even I already provide a certificate to access the cluster foo.
I have tries followings but all failed:
only usinc CLI is OK.
What happens behind the scene?
Beta Was this translation helpful? Give feedback.
All reactions