-
Notifications
You must be signed in to change notification settings - Fork 556
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
API Evolution for VPC and Networking Topologies #1484
Comments
@fabriziopandini if you have any thoughts on this, would be appreciated. |
@randomvariable I have something similar in the radar, but I dubt we can workout details during this iteration
In order to ^^^, it should be defined a way for clusterctl to interact with each provider while creating the cluster template, because the providers are the owner of the knowledge of what can be configured or not, and considering this should be accepted by each provider, I assume this requires a CAEP |
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. |
/lifecycle frozen |
@richardcase Would be useful to get the requirements for EKS down. I would have thought we can make EKS work with the existing topology. |
@randomvariable - i'll start documenting the requirments. The current default topology doesn't work as the 2 subnets it creates (1 public & 1 private) are in a single az and EKS requires subnets in at least 2 azs. |
https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html It would include stuff from there and other requirements. |
I've been asked to document our specific topology in here (ref: https://kubernetes.slack.com/archives/CD6U2V71N/p1588804729193200) Our starting point in the account is that a Direct Connect Gateway (DXG) exists. What we would need CAPA be able to do is:
|
/assign |
/assign @voor |
@randomvariable: GitHub didn't allow me to assign the following users: voor. Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
/lifecycle active (only from a gathering thoughts perspective) Will be sharing a Google Doc with initial ideas in a little while. Will definitely be towards v1alpha4 though. |
/triage accepted |
Another use case is using only public subnets: #2997 |
kinda related #3035 |
/remove-lifecycle frozen |
/milestone v2.x |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten Still relevant and related to #3711 |
Also relevant: #4026 |
Some thoughts: We'd probably want to also reason in terms of Control Plane vs Data Plane networking and how konnectivity enables that. |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/triage accepted |
/kind feature
Describe the solution you'd like
There are differing options on how to run Kubernetes clusters in AWS, these include:
How does a user figure out what one to use, and how best can we enable them?
Related issues include:
#931, #1208 , #1158 , #1062 , #1727
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
A proposal for this should include a evolutionary roadmap as far as the API goes. What are the most immediate concerns that can be addressed as additions to the v1alpha3 API, and what should be best considered as a breaking API changes.
The text was updated successfully, but these errors were encountered: