-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use ipv6 literal as system-default-registry #9924
Milestone
Comments
I need this for testing IPv6-only clusters, as I don't have external ipv6 connectivity in my environment :/ |
This was referenced Apr 11, 2024
Validated on master branch with commit 06b6444Environment DetailsInfrastructure
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Config.yaml:
Testing Steps
Replication Results:
Validation Results:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
K3s Version: v1.29.3+k3s1
Node(s) CPU architecture, OS, and Version:
n/a
Cluster Configuration:
n/a
Describe the bug:
Cannot use ipv6 literal as system-default-registry
Steps To Reproduce:
start k3s with ipv6 address as system-default-registry, for example:
k3s server --system-default-registry=[fd7c:53a5:aef5::242:ac11:7]
Expected behavior:
works
Actual behavior:
Errors in logs due to image name in pod spec not being quoted:
I0411 08:38:18.324145 54 event.go:376] "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"
The image value should be quoted, otherwise the square brackets are invalid yaml.
Additional context / logs:
The text was updated successfully, but these errors were encountered: