-
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
Introduce --insecure-skip-tls-verify
option for self-signed HTTP git URLs
#1513
Comments
This bug is invalid. For https URLs, the solution is to supply the self-signed certificates of the repo-server and api-server. Otherwise we can decide to introduce an I will convert this bug to an enhancement for that request. |
--insecure-ignore-host-key
option does not work for HTTP git URLs--insecure-skip-tls-verify
option for self-signed HTTP git URLs
@jessesuen Having a way to add insecure https git repos would be great. In my case, I don't use argocd cli at all. Another option could be to add a field for pasting your CA in ArgoCD UI's when adding a git repo. That's the way Rancher-UI handles custom CA's for pipelines. |
See #1805 |
PR is in progess |
…es (#1934) * Make sure insecure flag works for remote Kustomize bases
Done! Thanks to @jannfis for implementing it. |
|
Describe the bug
It is impossible to connect repositories using HTTP git url if git server uses self-signed certificate.
To Reproduce
Steps to reproduce the behavior:
argocd repo add https://<url> --username <username> --password <password> --insecure-ignore-host-key
x509: cannot validate certificate for <host> because it doesn't contain any IP SANs
Expected behavior
Repository should be successfully connected.
The text was updated successfully, but these errors were encountered: