-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Move DNS records from base_domain to cluster_domain #1169
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
Changes from all commits
3f7f0c9
6538030
1ab1cd3
2a0f9b3
bab6085
a0a77ad
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,8 @@ | ||
| locals { | ||
| new_private_cidr_range = "${cidrsubnet(data.aws_vpc.cluster_vpc.cidr_block,1,1)}" | ||
| new_public_cidr_range = "${cidrsubnet(data.aws_vpc.cluster_vpc.cidr_block,1,0)}" | ||
|
|
||
| cluster_domain = "${var.cluster_name}.${var.base_domain}" | ||
|
||
| } | ||
|
|
||
| resource "aws_vpc" "new_vpc" { | ||
|
|
@@ -9,7 +11,7 @@ resource "aws_vpc" "new_vpc" { | |
| enable_dns_support = true | ||
|
|
||
| tags = "${merge(map( | ||
| "Name", "${var.cluster_name}.${var.base_domain}", | ||
| "Name", "${local.cluster_domain}", | ||
| ), var.tags)}" | ||
| } | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -65,7 +65,7 @@ func (d *DNS) Generate(dependencies asset.Parents) error { | |
| // not namespaced | ||
| }, | ||
| Spec: configv1.DNSSpec{ | ||
| BaseDomain: installConfig.Config.BaseDomain, | ||
| BaseDomain: installConfig.Config.ClusterDomain(), | ||
|
||
| }, | ||
| } | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This package could be adjusted to take the unsplit cluster domain if we replaced this with Go logic to snip subdomains off the full cluster name until we found a public zone. Or we could restructure the install-config to make the public zone's domain part of the AWS-specific platform configuration. Both of those are probably more work than we want to sink into initial exploration, but I thought I'd file a note to track future polish possibilities ;).