Repository navigation
REQUEST: Netlify - Add custom domain for dranet.netlify.app #6451
Description
Repository
https://github.com/kubernetes-sigs/dranet
Project domain
dranet.sigs.k8s.io
Additional context for request
We have the dranet.dev domain which we'd like to add as a custom domain within the netlify setup of dranet.netlify.app. The domain dranet.dev has already been configured to point to netlify 75.2.60.5 as per instruction from https://docs.netlify.com/manage/domains/configure-domains/configure-external-dns/
I think the instructions that can be used to achieve addition of this new domain dranet.dev are available at https://docs.netlify.com/manage/domains/manage-domains/assign-a-domain-to-your-site-app/. We'll need someone with k8s netlify access to make this addition.
Activity
aojea commentedon Jun 18, 2026
/lgtm
dims commentedon Jun 18, 2026
@gauravkghildiyal it's self-service :) see kubernetes/k8s.io#9357
dims commentedon Jun 18, 2026
/transfer k8s.io
gauravkghildiyal commentedon Jun 18, 2026
Hey @dims, thanks for looking :)
So actually this request is different.
The request here is focused on point 2 above.
Question: Does it make sense to keep this request in kubernetes/org where netlify related requests are made?
dims commentedon Jun 18, 2026
/transfer org
aojea commentedon Jun 28, 2026
I think this is already done and we can close
/close
kubernetes-prow commentedon Jun 28, 2026
@aojea: Closing this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
palnabarun commentedon Jun 28, 2026
I don't see dranet.dev as an alias for the project.
gauravkghildiyal commentedon Jun 29, 2026
@palnabarun Yes this is still pending. Can you help with this?
(Don't have permission to reopen the issue)
palnabarun commentedon Jun 30, 2026
I have the permissions to add the domain. I would want to check whether we typically allow a non-CNCF owned domain to be served from our Netlify.
@natalisucks @divya-mohan0209 @reylejano -- as Netlify admin counterparts from SIG Docs, what's your view on this?
/reopen
(about the reopen perms, one can always reopen an issue with the slash command)
kubernetes-prow commentedon Jun 30, 2026
@palnabarun: Reopened this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
aojea commentedon Jun 30, 2026
Sorry about this, I totally missed the old domain, I thought we were orphaning it. Thanks Gaurav for following up
natalisucks commentedon Jun 30, 2026
@palnabarun as per @gauravkghildiyal's comment above, it looks like they're working on transferring the domain to CNCF. if that's taking place, then waiting until the transfer happens to serve from Netlify means there's no exception to policy/rule.
@gauravkghildiyal do you have a timeline on the transfer to CNCF?
thisisnotapril commentedon Jul 7, 2026
I am working on getting this domain along with a couple others transferred to CNCF; hopefully it will just be a week or so - I will keep y'all posted!
k8s-triage-robot commentedon Oct 22, 2026
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
palnabarun commentedon Oct 27, 2026
/remove-lifecycle stale
@thisisnotapril 👋🏽 did you end up transferring the domain to CNCF?