Environmental Info: K3s Version: $ k3s -v

containerd does not fall back to default endpoint when using wildcard registry entry about k3s HOT 1 CLOSED

VestigeJ commented on July 23, 2024

containerd does not fall back to default endpoint when using wildcard registry entry

from k3s.

Comments (1)

VestigeJ commented on July 23, 2024

##Environment Details
Validated using COMMIT=bba3e3c66b22bbf112dc316a9b5dbd27f68f4ba8

Infrastructure

Cloud

Node(s) CPU architecture, OS, and version:

Linux 5.14.21-150500.53-default x86_64 GNU/Linux
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"

Cluster Configuration:

$ kgn

NAME               STATUS   ROLES                       AGE     VERSION
ip-11-2-3-101      Ready    control-plane,etcd,master   6m22s   v1.29.2+k3s-bba3e3c6

Config.yaml:

node-external-ip: 11.2.3.101
token: YOUR_TOKEN_HERE
write-kubeconfig-mode: 644
debug: true
protect-kernel-defaults: true
cluster-init: true
embedded-registry: true

Reproduction

$ curl https://get.k3s.io --output install-"k3s".sh
$ sudo chmod +x install-"k3s".sh
$ sudo groupadd --system etcd && sudo useradd -s /sbin/nologin --system -g etcd etcd
$ sudo modprobe ip_vs_rr
$ sudo modprobe ip_vs_wrr
$ sudo modprobe ip_vs_sh
$ sudo printf "on_oovm.panic_on_oom=0 \nvm.overcommit_memory=1 \nkernel.panic=10 \nkernel.panic_ps=1 \nkernel.panic_on_oops=1 \n" > ~/90-kubelet.conf
$ sudo cp 90-kubelet.conf /etc/sysctl.d/
$ sudo systemctl restart systemd-sysctl
$ COMMIT=bba3e3c66b22bbf112dc316a9b5dbd27f68f4ba8
$ sudo vim /etc/rancher/k3s/registries.yaml
$ sudo INSTALL_K3S_COMMIT=$COMMIT INSTALL_K3S_EXEC=server INSTALL_K3S_SKIP_ENABLE=true ./install-k3s.sh
$ sudo vim /etc/systemd/system/k3s.service.env
$ sudo systemctl start k3s
$ kgp -A
$ kgn
$ sudo cat /var/lib/rancher/k3s/agent/etc/containerd/certs.d/_default/hosts.toml

Results:

$ kgp -A

NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   coredns-6799fbcd5-vkbtv                   1/1     Running     0          8m11s
kube-system   helm-install-traefik-crd-zvkm8            0/1     Completed   0          8m12s
kube-system   helm-install-traefik-x8zd6                0/1     Completed   1          8m12s
kube-system   local-path-provisioner-6c86858495-z4mcv   1/1     Running     0          8m11s
kube-system   metrics-server-54fd9b65b-kq279            1/1     Running     0          8m11s
kube-system   svclb-traefik-e3b71e6f-6w4vw              2/2     Running     0          7m58s
kube-system   traefik-f4564c4f4-7zsj5                   1/1     Running     0          7m58s

$ sudo cat /etc/rancher/k3s/registries.yaml

mirrors:
  "*":

note the below file now has the server = "" by default without any intervention from the admin
$ sudo cat /var/lib/rancher/k3s/agent/etc/containerd/certs.d/_default/hosts.toml

# File generated by k3s. DO NOT EDIT.

server = ""
capabilities = ["pull", "resolve", "push"]



[host."https://127.0.0.1:6443/v2"]
  capabilities = ["pull", "resolve"]
  ca = ["/var/lib/rancher/k3s/agent/server-ca.crt"]
  client = [["/var/lib/rancher/k3s/agent/client-k3s-controller.crt", "/var/lib/rancher/k3s/agent/client-k3s-controller.key"]]

from k3s.

Recommend Projects