krr: krr cannot connect to clusters using certificates signed by a private CA, stored in system CA store
Describe the bug A clear and concise description of what the bug is.
To Reproduce
- Set up a Kubernetes cluster with the API server certificate signed by a private CA
- Add the private CA to your system CA management tool (platform specific)
- Add the cluster into your kubeconfig, don’t explicitly provide the CA
Expected behavior
krr should be able to connect to the cluster, just as kubectl is able to.
Logs
on 0: [INFO] Listing scannable objects in private-cluster
on 0: [ERROR] Error trying to list hpa in cluster private-cluster:
HTTPSConnectionPool(host='controller.private-cluster.com', port=443): Max retries exceeded with url:
/apis/autoscaling/v2/horizontalpodautoscalers?watch=False (Caused by SSLError(SSLCertVerificationError(1, '[SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))
on 0: [ERROR] Will assume that there are no HPA. Be careful as this may lead to inaccurate results if object actually has HPA.
Desktop (please complete the following information):
- OS: MacOS 13.5.2
- Version KRR 1.6.0
Additional context
Even providing an “insecure” option would be helpful. Right now I need to run a local proxy that krr can connect to, which is a pain.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 1
- Comments: 15 (6 by maintainers)
Just add insecure-skip-tls-verify: true inside cluster item in your kubeconfig file.