[Umbrella issue] Automate DNS for Kubernetes assets about k8s.io HOT 11 CLOSED

cc @justinsb @brendandburns @thockin @hh @spiffxp

from k8s.io.

Annotated TODOs from the README:

• Get owner names and comments on all records: Willing to proceed without full coverage of names

• Push an official image to GCR: thockin will do as soon as we are ready to go live

• When to rebuild?: Not sure. Maybe just leave it alone and update when we know we need to? Low risk as long as pushes are manual.

• Implement the test part of the push script: Assigned to @hh (please confirm?). @thockin is willing to do this if @hh can't get to it.

• Document how to handle "too many" updates (--force): Punt for now and cross that bridge when we get there

• Always --force?: (see above)

• Billing report: assigned to @idvoretskyi, but we should proceed without this (not a technical issue with the serving path)

• Usage report: willing to proceed without this

• Monitoring / alerts / on-call: We have an alerts group, but we don't have any probes for DNS. Could use a volunteer on this, but willing to proceed without it?

• Figure out who to contact to flip top-level NS records: thockin will do when we are ready

So the only outstanding issue is integrating a canary test in the push script. @hh, ball is in your court. If you want to punt the test, just say so. Otherwise - eta for something we can start to discuss?

from k8s.io.

Digging into two built in options:

https://github.com/github/octodns/blob/master/octodns/cmds/report.py
https://github.com/github/octodns/blob/master/octodns/cmds/compare.py

from k8s.io.

@hh I want to be respectful of your interest, but I also want to close this issue and activate the new DNS. Can you have this test wrapped by mid-month? Otherwise I am going to take a crack at it.

Happy new year!

from k8s.io.

Sorry for the delay, see #161.

from k8s.io.

/assign @thockin @dims

from k8s.io.

/assign @hh @thockin

from k8s.io.

@thockin if do you want to try and apply #162 using the new push/test scripts?

from k8s.io.

next steps?

• cluster?
• wait until prow?
• if someone files an issue, people in the OWNERS file can push a PR, once the PR is merged, "we = k8s-infra-dns-admins googlegroup" can run a command which canaries and pushes to prod

from k8s.io.

/close
I'm closing this as implemented well enough for proof of concept, and opened up #239 for followup work to automate this further such that it becomes self-service

from k8s.io.

@spiffxp: Closing this issue.

from k8s.io.