[Release-1.27] - Cannot use ipv6 literal as system-default-registry

[brandond]

Backport fix for Cannot use ipv6 literal as system-default-registry

• Cannot use ipv6 literal as system-default-registry #9924

[aganesh-suse]

Validated on release-1.27 branch with commit 2d48b19

Environment Details

Infrastructure

• Cloud
• Hosted

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

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"

$ uname -m
x86_64

Cluster Configuration:

HA: 3 server/ 1 agent

Config.yaml:

token: xxxx
cluster-init: true
system-default-registry: "[fd7c:53a5:aef5::242:ac11:7]"
write-kubeconfig-mode: "0644"
node-external-ip: 1.1.1.1
node-label:
- k3s-upgrade=server

Testing Steps

1. Copy config.yaml

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

2. Install k3s

curl -sfL https://get.k3s.io | sudo INSTALL_K3S_COMMIT='2d48b19624efec5082f1864e64f3a13ca4124354' sh -s - server

3. Check the image is with double quotes for ipv6 in all yaml files and that there are no parse manifest errors:

$ sudo journalctl -xeu k3s | grep coredns | grep ParseManifestFailed
$ sudo grep image: /var/lib/rancher/k3s/server/manifests/coredns.yaml
$ sudo grep -rni image: /var/lib/rancher/k3s/server/manifests

Replication Results:

• k3s version used for replication:

$ k3s -v
k3s version v1.27.12+k3s1 (78ad5756)
go version go1.21.8

 $ sudo journalctl -xeu k3s | grep coredns | grep ParseManifestFailed 
Apr 16 21:10:43 ip-172-31-21-32 k3s[84375]: I0416 21:10:43.796755   84375 event.go:307] "Event occurred" object="kube-system/coredns" fieldPath="" kind="Addon" apiVersion="k3s.cattle.io/v1" type="Warning" reason="ParseManifestFailed" message="Parse manifest at \"/var/lib/rancher/k3s/server/manifests/coredns.yaml\" failed: yaml: line 44: did not find expected key"

 $ sudo grep image: /var/lib/rancher/k3s/server/manifests/coredns.yaml 
        image: [fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-coredns-coredns:1.10.1

 $ sudo grep -rni image: /var/lib/rancher/k3s/server/manifests
/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-deployment.yaml:47:        image: [fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-metrics-server:v0.7.0
/var/lib/rancher/k3s/server/manifests/local-storage.yaml:70:        image: [fd7c:53a5:aef5::242:ac11:7]/rancher/local-path-provisioner:v0.0.26
/var/lib/rancher/k3s/server/manifests/local-storage.yaml:158:        image: [fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-library-busybox:1.36.1
/var/lib/rancher/k3s/server/manifests/traefik.yaml:28:    image:
/var/lib/rancher/k3s/server/manifests/coredns.yaml:123:        image: [fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-coredns-coredns:1.10.1

Validation Results:

• k3s version used for validation:

$ k3s -v
k3s version v1.27.12+k3s-2d48b196 (2d48b196)
go version go1.21.8

$ sudo journalctl -xeu k3s | grep coredns | grep ParseManifestFailed

 $ sudo grep image: /var/lib/rancher/k3s/server/manifests/coredns.yaml
        image: "[fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-coredns-coredns:1.10.1"

 $ sudo grep -rni image: /var/lib/rancher/k3s/server/manifests
/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-deployment.yaml:47:        image: "[fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-metrics-server:v0.7.0"
/var/lib/rancher/k3s/server/manifests/local-storage.yaml:70:        image: "[fd7c:53a5:aef5::242:ac11:7]/rancher/local-path-provisioner:v0.0.26"
/var/lib/rancher/k3s/server/manifests/local-storage.yaml:159:        image: "[fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-library-busybox:1.36.1"
/var/lib/rancher/k3s/server/manifests/traefik.yaml:29:    image:
/var/lib/rancher/k3s/server/manifests/coredns.yaml:123:        image: "[fd7c:53a5:aef5::242:ac11:7]/rancher/mirrored-coredns-coredns:1.10.1"