Proxy not handled properly in combination with RKE2

[koendelaat]

When configuring a HTTP(S)_PROXY in EIB, this configures the OS proxy settings and works for K3s to pull images

However, when using RKE2 this is not the case.

According to the two sections in the docs there is a different behavior during installation

K3s

The K3s installation script will automatically take the HTTP_PROXY, HTTPS_PROXY and NO_PROXY, as well as the CONTAINERD_HTTP_PROXY, CONTAINERD_HTTPS_PROXY and CONTAINERD_NO_PROXY variables from the current shell, if they are present, and write them to the environment file of your systemd service, usually:

/etc/systemd/system/k3s.service.env
/etc/systemd/system/k3s-agent.service.env
Of course, you can also configure the proxy by editing these files.

RKE2

Add the necessary HTTP_PROXY, HTTPS_PROXY and NO_PROXY variables to the environment file of your systemd service, usually:

/etc/default/rke2-server
/etc/default/rke2-agent