When the operator creates the pod containing the baseiso container via fleet, there is no way to provide proxy configuration either via rancher, or via Helm that I could find.
The Containing K3s node does of course not inject any proxy variables into the container, and I would prefer not to create an admission-controller if at all possible.
The documents in https://elemental.docs.rancher.com/elemental_behind_proxy/ only describe adjustments that concern Nodes or Clusters running a completed image, not how to configure the baseiso container.
I apologize if I am missing something obvious, but I see no way to configure this behaviour, or injecting a /etc/sysconfig/proxy file into the baseiso container.
When the operator creates the pod containing the baseiso container via fleet, there is no way to provide proxy configuration either via rancher, or via Helm that I could find.
The Containing K3s node does of course not inject any proxy variables into the container, and I would prefer not to create an admission-controller if at all possible.
The documents in https://elemental.docs.rancher.com/elemental_behind_proxy/ only describe adjustments that concern Nodes or Clusters running a completed image, not how to configure the baseiso container.
I apologize if I am missing something obvious, but I see no way to configure this behaviour, or injecting a /etc/sysconfig/proxy file into the baseiso container.