Hi Jay, as Phil said we haven’t purposely configured anything to avoid this, and haven’t seen this issue when connecting to a R53 private zone CNAME using clients for SSL and STOMP-SSL on 3 different languages.
Out of curiosity, are you using public or private DNS?
Hey Adam, good question, perhaps I could clarify that bit on the repo readme.
s3_buckets.tf file is actually for the kops state. Terraform remote state is referenced on
main.tf as you pointed out, and it’s actually a good idea to manage it through a different terraform project, or just have the S3 bucket…
Hey Mark, thanks for the note! You are right, it should be
private_subnet_ids matching the Terraform output. I’ll push an updated version to Git. Thank you!
Thanks Ionut! Great article and nice approach. Have you considered using
--target terraform when running
kops update? Having the k8s cluster being an entity on Terraform has proven handy to us for things like referencing cluster resources in other tf projects and it’s also pretty sweet to be able to run
terraform plan for cluster changes.