Closed RaSerge closed 1 month ago
I will try to implement work from this PR https://github.com/aenix-io/cozystack/pull/175
I think the easiest way at the moment is to specify registry-mirrors in talos configuration
Also installation image as well the others, can be specified using talos machine config, eg:
machine:
kubelet:
image: ghcr.io/siderolabs/kubelet:v1.29.0-rc.1
install:
image: ghcr.io/siderolabs/installer:v1.6.0-beta.1
apiServer:
image: registry.k8s.io/kube-apiserver:v1.29.0-rc.1
controllerManager:
image: registry.k8s.io/kube-controller-manager:v1.29.0-rc.1
proxy:
image: registry.k8s.io/kube-proxy:v1.29.0-rc.1
scheduler:
image: registry.k8s.io/kube-scheduler:v1.29.0-rc.1
etcd:
image: gcr.io/etcd-development/etcd:v3.5.11-arm64
Thank you!
Hello! I'm tried to adopt talm for air-gapped lab installation. by define ntp servers, registries mirrors and upload images from
talosctl image default
It seems that talm installation dont't use that images (registry download metrics counters at 0) Which default images version we should have in local registry? Can you provide some additional info how to adapt talm installation for air-gapped environment,