Losing .io domains?

[Tim Hockin]

https://every.to/p/the-disappearance-of-an-internet-domain

Maybe we should lock down some good alternatives?

[Jaice Singer DuMars]

I still have k8s.sh that I can donate to the project.

On Tue, Oct 8, 2024 at 6:24 PM 'Tim Hockin' via steering <stee...@kubernetes.io> wrote:

https://every.to/p/the-disappearance-of-an-internet-domain

Maybe we should lock down some good alternatives?

--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAO_RewaqYuPkdPR%2BtSg8sxe4HWUQRAFMvRVdP03X-n8cAAU2PA%40mail.gmail.com.

[Bob Killen]

we do have k8s.dev and IIRC are sitting on a few others as well.

To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAJHHSLxaooTHQN90%2B0KxhP7QkPEHW81HDKjVk9-nmUKpdxBjbQ%40mail.gmail.com.

[Benjamin Elder]

.dev would be good but ... we're using k8s.dev for other (contributor facing) content already? e.g. k8s.dev/release != k8s.io/release

We need to be able to potentially move all the *.k8s.io endpoints without conflict ...

Also, if we think something like this is likely, we should be bracing for another round of notifying users and redirecting all the things.

We probably shouldn't have ever adopted .io but ... that's history now.

Migrating will be very painful.
Having a reserved alias live in place ahead of time would help.

I would not pick another country code TLD.

To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAJ18wa_yJwHOVem7SvH%3DjPOcoycLatVejUx5aObesM%2BUxTYCLA%40mail.gmail.com.

[Antonio Ojea]

For reference https://github.com/kubernetes/k8s.io/tree/main/dns#managing-dns-for-kubernetes-domains

I'm confused with the linked article from the comments
https://www.computerworld.com/article/3552692/is-the-io-top-level-domain-headed-for-extinction.html
, it seems the removal of .io is not definitive and there may be
different outcomes, though I agree we should have a plan considering
.io will be shutdown.

> To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAOZRXm88tjxBH%3DGxmhSWUz1P5w8Jk1GRQbLXkt8ki3zM0u_iSQ%40mail.gmail.com.

[Tim Bannister]

Hello Steering.

AIUI: we have five years at least, but: they'll go sooner than we think.

Tim Bannister

Senior consultant specialist

The Scale Factory

[Davanum Srinivas]

Folks,

FYI opened an issue here: https://github.com/kubernetes/kubernetes/issues/127966

--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.

To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/5b1f7ad3-fa56-4767-99ca-aaf4f90f2928n%40kubernetes.io.

--

Davanum Srinivas :: https://twitter.com/dims

[Benjamin Elder]

Hi all, I've drafted a proposal on the issue here: https://github.com/kubernetes/kubernetes/issues/127966#issuecomment-2402958359

It has a few remaining open questions, PTAL

CC +kubernetes-sig-k8s-infra +kubernetes-sig-contribex +kubernetes-sig-architecture for visibility (please discuss in the github issue to avoid further fragmenting the discussion)

[Benjamin Elder]

FYI also +kubernetes-sig-release, see above folks!

[Benjamin Elder]

ACK - As discussed in the issue, we don't necessarily think this is guaranteed to happen, but others have also pointed out that .io has not necessarily been well-managed.

However, past experience tells us that we users need quite a lot of time to migrate (downloads/images etc), so preemptively hedging is probably wise, beyond just planning.

On Wed, Oct 9, 2024 at 11:53 AM Taahir Ahmed <ta...@google.com> wrote:

The article is needlessly alarmist --- the IANA can (and has in the past) retained country codes after dissolution of the corresponding entity, and given them over to a successor entity to manage.

However, it's still good to plan out what we would have to do in order to migrate (especially since *.io has not historically been a particularly well-managed country code).

You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CAOZRXm8vUu1ShXOaJG-bh-pRYOcq1fEJ2V%3D%2BefqKSFogD%2BvBdA%40mail.gmail.com.

[Sean McGinnis]

Also note that this is not a matter of the "dissolution" of an entity or poor management. There is a fundamental issue with the way .io has been used to date. So I think this goes a little beyond IANA transferring ownership to better management.

https://www.drawio.com/blog/move-diagrams-net

So whether .io does end up sticking around as a viable TLD for the project to use or not, I do think it makes sense as a community to come up with a plan to migrate away from it to something less problematic.

You received this message because you are subscribed to the Google Groups "kubernetes-sig-k8s-infra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-k8s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-k8s-infra/CAOZRXm8MC7PCZW7vdY9jae%2BGVNKkHH%2BpZXipSB9xy2%3DrOmsbFw%40mail.gmail.com.

[Taahir Ahmed]

The article is needlessly alarmist --- the IANA can (and has in the past) retained country codes after dissolution of the corresponding entity, and given them over to a successor entity to manage.

However, it's still good to plan out what we would have to do in order to migrate (especially since *.io has not historically been a particularly well-managed country code).

On Wed, Oct 9, 2024 at 11:46 AM 'Benjamin Elder' via kubernetes-sig-architecture <kubernetes-si...@googlegroups.com> wrote:

You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CAOZRXm8vUu1ShXOaJG-bh-pRYOcq1fEJ2V%3D%2BefqKSFogD%2BvBdA%40mail.gmail.com.

[Maciej Szulik]

Antonio also pointed out in one of the messages we have this list of domains:

> For reference https://github.com/kubernetes/k8s.io/tree/main/dns#managing-dns-for-kubernetes-domains

Which states we also own etcd.io, so eventual contingency plans should
accommodate that
and potentially other domains we control. I hope all are listed in the
above doc.

cc etcd-dev


On Wed, Oct 9, 2024 at 8:46 PM 'Benjamin Elder' via
kubernetes-sig-architecture

> You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CAOZRXm8vUu1ShXOaJG-bh-pRYOcq1fEJ2V%3D%2BefqKSFogD%2BvBdA%40mail.gmail.com.

[Maciej Szulik]

Now, with fixed etcd-dev email