Skip to content
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

Pull kn.dev into knative-dns project #3299

Closed
2 of 3 tasks
hh opened this issue Apr 28, 2022 · 7 comments
Closed
2 of 3 tasks

Pull kn.dev into knative-dns project #3299

hh opened this issue Apr 28, 2022 · 7 comments
Assignees
Labels
area/gcp Issues or PRs related to Google Cloud Infrastructure priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@hh
Copy link

hh commented Apr 28, 2022

#3134 (comment)

When I was at Google I also scooped kn.dev for Knative, if it's easy enough to transfer that, I'd suggest it as well.

@chizhg chizhg changed the title Pull kn.dev into knative-dns project Pull kn.dev and kn-e2e.dev into knative-dns project Apr 28, 2022
@chizhg
Copy link
Member

chizhg commented Apr 28, 2022

There is also a kn-e2e.dev domain which is used by the auto TLS e2e test - https://github.com/knative/serving/blob/main/test/e2e-auto-tls-tests.sh#L27

@upodroid upodroid changed the title Pull kn.dev and kn-e2e.dev into knative-dns project Pull kn.dev into knative-dns project May 23, 2022
@upodroid
Copy link
Member

@thisisnotapril @mattmoor @hh Can we initiate the transfer of ownership for kn.dev and kn-e2e.dev?

Please use the following NS Records:

kn.dev
ns-cloud-c1.googledomains.com. 
ns-cloud-c2.googledomains.com. 
ns-cloud-c3.googledomains.com. 
ns-cloud-c4.googledomains.com.
kn-e2e.dev
ns-cloud-e1.googledomains.com.
ns-cloud-e3.googledomains.com.
ns-cloud-e4.googledomains.com.
ns-cloud-e2.googledomains.com.

@upodroid upodroid added area/gcp Issues or PRs related to Google Cloud Infrastructure priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Jun 13, 2022
@upodroid
Copy link
Member

Google handed the xfer codes to LF. This should be done later this week and LF will modify the domain to use the correct NS servers.

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 14, 2022
@upodroid
Copy link
Member

@hh What is the latest on this ticket?

@hh
Copy link
Author

hh commented Sep 14, 2022

We had an issue were the domain's were not yet active when I did the initial request.
I verified that they were under LF control and have created two new LF IT tickets for the final stage of transition:

IT-24536 - kn.dev NS records update
IT-24537 - kn-e2e.dev NS records update

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 15, 2022
@upodroid
Copy link
Member

This is done now.

Thanks

 REDACTED  MCW0CDP3YY  ~  $  dig ns kn-e2e.dev +short
ns-cloud-e2.googledomains.com.
ns-cloud-e1.googledomains.com.
ns-cloud-e4.googledomains.com.
ns-cloud-e3.googledomains.com.
 REDACTED  MCW0CDP3YY  ~  $  dig ns kn.dev +short
ns-cloud-c4.googledomains.com.
ns-cloud-c2.googledomains.com.
ns-cloud-c3.googledomains.com.
ns-cloud-c1.googledomains.com.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gcp Issues or PRs related to Google Cloud Infrastructure priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

3 participants