-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Terraform Doesn't Work With Private Hosted Zones #1885
Comments
I've the same issue, with private or public Route53 zone, I'm receving the same error.
The same command without |
Im getting the same issue, kops 1.5.1
|
@justinsb any ideas? |
Any updates here? I am having the same issue |
I believe this is a duplicate of #1848. There is a concern around how to "manage" or "acquire" information about that private hosted zone with Terraform in a repeatable and safe way. |
I ended up setting up my VPC, subnets, route tables, DNS private zone, ... manually with terraform. In my kops kops create cluster command I specified my VPC, network and private dns zone created by terraform. I didn't specify terraform output here. After the creation, I've updated the cluster configuration so that the subnets match the ones I 've created.
After that I applied the changes. At this point I can manage my kubernetes resources with kops and my other resources with terraform. I found most of the required info to get here in this post https://github.com/kubernetes/kops/blob/master/docs/run_in_existing_vpc.md |
I believe this has been addressed in #2297 |
This issue is still happening in 1.6.1 |
Just tried with: |
Closing, please use 1.7.1 kops, as it has a cve patch in it |
Running the simple
I am using kops 1.8.0. |
kops 1.8.1 the same.
Output:
Zone exist |
Had the same issue before payed attention to the following statement:
|
I am attempting to use kops a private topology cluster with a private dns, however I receive the message
Route53 private hosted zones are not supported for terraform
. It is unclear if this means I need to instead create Route53 entries manually prior to trying to export to TF using kops, or if kops is just unable to run this command at all.The text was updated successfully, but these errors were encountered: