-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Allow specifying dns-name separately? #12
Comments
Why does this matter? Or does globally here mean within the same AWS account? |
What is the distinction between this and the "--dns-zone" argument? |
Seems like maybe there should be a |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
…re/merge_dcos_nfl_ncaaf_restnew to feature/merge_dcos_nfl_ncaaf * commit '5f79821febb5681ced2767c1f813afc639b51ea7': NFL Category added for REST APIs
…acenter from feature/create_cluster_from_kops to develop * commit '3ca57ad2a7a10988df5319d7a9d1ef544e5a13fc': Update aws command
…elop to master * commit '34d492a75600750958d25f954195c55a39f02be6': Add docker image for building other docker containers
Maybe we should allow the ClusterName to be different from the DNS name. Users will likely want to specify a shorter name, for example. And this means we're less bound to DNS at the schema level.
On the flip side, it means cluster names are no longer globally unique.
The text was updated successfully, but these errors were encountered: