-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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 VPC lookup should not use tag filtering #14466
Labels
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
chris-codaio
added a commit
to chris-codaio/kubernetes
that referenced
this issue
Sep 24, 2015
…up which VPC an AWS node is attached to.
bgrant0607
added
priority/backlog
Higher priority than priority/awaiting-more-evidence.
team/community
labels
Sep 24, 2015
Merged
ananth-at-camphor-networks
pushed a commit
to Juniper/kubernetes
that referenced
this issue
Oct 3, 2015
…up which VPC an AWS node is attached to.
mkulke
pushed a commit
to mkulke/kubernetes
that referenced
this issue
Oct 7, 2015
…up which VPC an AWS node is attached to.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the AWS cloud provider's VPC lookup - given the vpc_id is being read directly from metadata from the local instance, there's no need to additionally filter on the KubernetesCluster tag. Not only is this superfluous, but it prevents sharing a single regional VPC with multiple per-AZ Kubernetes clusters (per best practices).
The text was updated successfully, but these errors were encountered: