-
Notifications
You must be signed in to change notification settings - Fork 804
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
DNS REQUEST: kubebuilder.io #6703
Comments
the config for this is in |
Hi @BenTheElder Thank you a lot for let me know. Could you please when you have time just give a hand where I should create it? I cannot find any record from the domains that we have already. |
Oh, sigh, kubebuilder.io is not a kubernetes owned domain, k8s.io, kubernetes.io and others are. |
We have: etcd.io I don't know who owns kubebuilder.io but I suspect it's not the CNCF or Kubernetes project, if it was it would be in |
The pattern we have for subproject docs is like http://kind.sigs.k8s.io (I helped establish this!), we have a shared netlify account that SIG docs can setup against a subdomain and the subdomains of sigs.k8s.io are self-service (or we can help you) in this repo. We don't take over whole new domains often and I'm not sure where we'd start there ... first we'd have to know who owns it and if they can transfer it. It may be easier to update the existing host to serve a redirect to a project controlled domain like kubebuilder.sigs.k8s.io |
Hi @BenTheElder Looking at whois: https://who.is/whois/kubebuilder.io it is register with the LinuxFoundation. We need help to know who can manage the DNS. Have you any clue? |
We can ping @jeefy, the CNCF liason for the Kubernetes project, but I would still recommend switching to kubebuilder.sigs.k8s.io so we can manage it like other subprojects. |
I think this was solved for now? |
Yes kudos for @jeefy !!! Thank you a lot folks for the help !!! |
Type of DNS update:
Update
Domain being modified:
kubebuilder.io
Existing DNS Record:
We use the domain
kubebuilder.io
to publish the docs.Then, we have entries to keep published OLD versions/legacy documentation
See:
We need a new entry because we will push a MAJOR release.
That means we need to add:
Reason for update:
After the MAJOR release Kubebuilder CLI 4x
We want to keep the legacy doc available for Kubebuilder CLI 3x
But we need the entry to be able to properly configure the book-v3 branch to server book-v3.book.kubebuilder.io -- legacy docs
@mrbobbytables can help us to configure the netlify but he has no access to the DNS to add the new entry.
The text was updated successfully, but these errors were encountered: