I am trying spin up a new node in an air-gapped en...
# rke2
e
I am trying spin up a new node in an air-gapped environment and I am having issues with some of the "core" pods being unable to pull images (understandably). How can I get around this? I doubt it matters, but this new node is a physical server while the other 7 nodes are all VM's.
specifically these are the images that appear unavailable:
Copy code
calico-system	<http://docker.io/rancher/mirrored-calico-pod2daemon-flexvol:v3.28.2|docker.io/rancher/mirrored-calico-pod2daemon-flexvol:v3.28.2>
calico-system	<http://docker.io/rancher/mirrored-calico-cni:v3.28.2|docker.io/rancher/mirrored-calico-cni:v3.28.2>
calico-system	<http://docker.io/rancher/mirrored-calico-node:v3.28.2|docker.io/rancher/mirrored-calico-node:v3.28.2>
kube-system		<http://index.docker.io/rancher/hardened-kubernetes:v1.29.12-rke2r1-build|index.docker.io/rancher/hardened-kubernetes:v1.29.12-rke2r1-build>
kube-system		rancher/nginx-ingress-controller:1.10.5-hardened3
I do not recall the magic incantations that made these work on the other nodes. Is there a way to pull the image from the other workers?
c
did you provide those nodes with the correct airgap image tarballs?
You need to either do that, or set up a private registry mirror outside the cluster, or enable use the embedded registry mirror: https://docs.rke2.io/install/registry_mirror
e
probably not
This server was built in the non-airgapped environment then moved over.
Thanks for the link. I will read up.
To follow up for anyone following this... make sure your RKE2 versions match...
works much better