Skip to content

Conversation

lf-
Copy link
Contributor

@lf- lf- commented Jun 24, 2025

2001:db8::/32 is the reserved documentation range, which should be used instead of a range that might be assigned to someone. See https://en.wikipedia.org/wiki/Reserved_IP_addresses#IPv6 for details.

We can't fix the v4 addresses since there are only some documentation /24s and nothing larger.

2001:db8::/32 is the reserved documentation range, which should be used instead of a range that might be assigned to someone.

We can't fix the v4 addresses since there are only some documentation /24s and nothing larger.

Signed-off-by: Jade Lovelace <[email protected]>
@brandond
Copy link
Member

brandond commented Jun 24, 2025

I HIGHTLY doubt 2001:cafe:: will be allocated to anyone. Note that 2001:db8:: and 2001:cafe:: are both part of the same 2001:c00::/23 block that is already marked as allocated as per
https://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xhtml

image

This entire block has been marked allocated since 2002.

@lf-
Copy link
Contributor Author

lf- commented Jun 26, 2025

Sure; my motivation here is that the addresses in the docs are obviously bogus and are forbidden from ever being routed externally even if anyone does copy paste them. It's not the first time that k8s has used internet real estate in examples which it was not supposed to (c.f. .local domains, which actually broke stuff).

It's more about conventions and avoiding using numbers we don't own even if it won't actually break something in practice.

@dereknola dereknola merged commit fee09e7 into k3s-io:main Jul 1, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants