https://rancher.com/ logo
#general
Title
# general
a

adamant-kite-43734

10/18/2022, 3:45 PM
This message was deleted.
d

damp-painting-69352

10/18/2022, 4:56 PM
You can get around this using the HelmChart CRD and apply the chart in base64 https://docs.rke2.io/helm/
you can do the same with helm directly
a

ancient-raincoat-46356

10/18/2022, 5:42 PM
That would seem to make chart updates a manual process, No offense but not a fan of that answer. I'd like to think that if Rancher is going to install the Helm Chart repo on the remote cluster, then the remote cluster should honor the environment variables for proxy either from the OS or from the K3s env file
/etc/default/k3s
. Perhaps if I had a technical breakdown of what Rancher is doing to execute these actions, I could figure out what is missing and where to make it honor using the proxy. I added these proxy env var's recently so maybe it's just a pod that needs to be restarted to pick those up but I don't know which pods (if any) Rancher is talking to on the remote cluster to go get this repo's index.yaml file.
d

damp-painting-69352

10/18/2022, 6:13 PM
Rancher's helm chart has no-proxy configuration options as well
which likely apply to rancher
a

ancient-raincoat-46356

10/18/2022, 6:44 PM
Do you know what is executing the equivalent
helm repo add ...
command on the remote cluster side? Something has to be making that call and failing to pull it because it's not routing through my proxy.
d

damp-painting-69352

10/18/2022, 6:46 PM
gitjob i think, part of fleet
did you update the rancher helm chart for no_proxy?
a

ancient-raincoat-46356

10/18/2022, 8:35 PM
I'll have to look into that. Not 100% clear what that entails but I will do the research and check on that suggestion. Thank you for your guidance.
23 Views