-
Notifications
You must be signed in to change notification settings - Fork 495
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
AWS EKS: unable to connect to the cluster with create_vpc=false and existing VPC #514
Comments
Hello, thank you for the report, we are looking into this issue and will update later. Your patience will be appreciated. |
Reusing existing VPC and subnets that created by Terraform for another EKS cluster is not supported now due to various limitations. However, it is possible to make the second cluster deployed by manually adding tag Note that this is not recommend and may cause dependency issues when trying to modify or destroy these resources. We have submitted PR to correctly put resources into public and private subnets, and to make the docs more clear on this kind of situation. |
* eks: Update the eks deployment doc Translate pingcap/docs-tidb-operator#421 * Address comments * Optimize wording Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com> Co-authored-by: Lilian Lee <lilin@pingcap.com>
Bug Report
What version of Kubernetes are you using?
AWS EKS 1.12 on us-east-2
What did you do?
What did you expect to see?
the second tidb cluster will be created inside the same VPC, but on a second EKS cluster
What did you see instead?
Unable to connect to the bastion host, because it went to the private subnet
From the tf code, seems that when create_vpc=false, we should use separate subnet id variables for bastion and EKS, so that bastion goes to the public subnet, EKS private?
https://github.com/pingcap/tidb-operator/blob/master/deploy/aws/main.tf#L72
https://github.com/pingcap/tidb-operator/blob/master/deploy/aws/main.tf#L89
The text was updated successfully, but these errors were encountered: