-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
modules/dns/route53: Tag the tectonic zone #158
Conversation
We've been tagging our internal zone since 75fb49a (platforms/aws: apply tags to internal route53 zone, 2017-05-02, coreos/tectonic-installer#465). Tagging this resource makes it easier to cleanup resource leaks, because the resource is more obviously associated with the given cluster (and you can use extra_tags to set expirationDate, etc.).
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The e2e-aws error was:
Maybe I accidentally removed a shared zone during my orphan-resource pruning? It doesn't look like we're providing our own zone. |
Checking if the "no matching Route53Zone" error is reproducible: /retest |
@wking: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
|
Because I'm touching a data block here, not a resource block. 🤦♂️ |
This commit adds the ability to pass custom userData/startupScripts to the machines using kubernetes secrets. The previous workflow that used the machine-setup ConfigMap has been removed in favor of the new one. Fixes openshift#158
We've been tagging our internal zone since 75fb49a (coreos/tectonic-installer#465). Tagging this resource makes it easier to cleanup resource leaks, because the resource is more obviously associated with the given cluster (and you can use
extra_tags
to setexpirationDate
, etc.).