-
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
Enable usage of AWS Transit Gateway #8837
Comments
/kind feature |
Issues go stale after 90d 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. |
/remove-lifecycle stale |
Issues go stale after 90d 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. |
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-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@rifelpet: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1. Describe IN DETAIL the feature/behavior/change you would like to see.
Cluster spec should allow the usage of AWS Transit Gateways, like it's possible to define
egress
to use specific NAT gateways (https://github.com/kubernetes/kops/blob/master/docs/cluster_spec.md#egress)I tried setting it to the resource
tgw-aedf1230
but validation of cluster spec fails with errorerror populating cluster spec: spec.Subnets[0].Egress: Invalid value: "tgw-aedf1230": egress must be of type NAT Gateway or NAT EC2 Instance or 'External'
2. Feel free to provide a design supporting your feature request.
Only the route table entry has to be changed for
0.0.0.0/0
to usetgw-aedf1230
aws resourceThe text was updated successfully, but these errors were encountered: