4. Install cert-manager and Rancher [following the steps for Rancher generated certificates or LE](https://rancher.com/docs/rancher/v2.x/en/installation/k8s-install/helm-rancher/)
**Result:**
Rancher Helm install fails with error:
Other details that may be helpful:
HTTP Proxy log shows that Kubernetes API server uses the Proxy to connect to the cert-manager webhook even though .svc domain is in the NO_PROXY exclude list.
CONNECT Apr 24 10:40:16 [30184]: Request (file descriptor 7): CONNECT cert-manager-webhook.cert-manager.svc:443 HTTP/1.1
INFO Apr 24 10:40:16 [30184]: No upstream proxy for cert-manager-webhook.cert-manager.svc
ERROR Apr 24 10:40:16 [30184]: opensock: Could not retrieve info for cert-manager-webhook.cert-manager.svc
INFO Apr 24 10:40:16 [30184]: no entity
What kind of request is this (question/bug/enhancement/feature request): Bug
Steps to reproduce (least amount of steps as possible):
tinyproxy
)$ systemctl restart k3s
$ helm install rancher rancher-latest/rancher \
Other details that may be helpful: HTTP Proxy log shows that Kubernetes API server uses the Proxy to connect to the cert-manager webhook even though
.svc
domain is in theNO_PROXY
exclude list.k3s api-server warning:
Environment information
rancher/rancher
/rancher/server
image tag or shown bottom left in the UI): 2.4.2