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: Shared resource tag #35052

Closed
austinmoore- opened this Issue Oct 18, 2016 · 2 comments

Comments

Projects
None yet
4 participants
@austinmoore-

austinmoore- commented Oct 18, 2016

In order to use some resources in AWS, Kubernetes currently requires "ownership" of the resource with the tag KubernetesCluster=<cluster_id>. However, some resources can belong to more than a single Kubernetes cluster. Resources could potentially be used by things outside of Kubernetes, or perhaps by other Kubernetes clusters one day. Once the KubernetesCluster tag is applied to these resources and a cluster has "ownership" over them, there is a potential that Kubernetes tools like kube-up or kops could modify or remove these resources.

A tag indicating that a resource is "shared" would be valuable. @justinsb has said that he thinks it should be something like kubernetes.io/<clustername>=shared.

It may be valuable to rethink the KubernetesCluster tag in general, keeping in mind use cases like shared resources and multiple cluster ownership (#22058).

@hjacobs

This comment has been minimized.

Show comment
Hide comment
@hjacobs

hjacobs Oct 25, 2016

@austinmoore- we are also running into a similar issue with the KubernetesCluster tag as we want to reuse our network setup (i.e. subnets). The AWS integration currently assumes only one cluster per subnet (subnets tagged with KubernetesCluster=...).

hjacobs commented Oct 25, 2016

@austinmoore- we are also running into a similar issue with the KubernetesCluster tag as we want to reuse our network setup (i.e. subnets). The AWS integration currently assumes only one cluster per subnet (subnets tagged with KubernetesCluster=...).

@justinsb

This comment has been minimized.

Show comment
Hide comment
@justinsb

justinsb Jun 13, 2017

Member

This is now implemented as @kenden pointed out here: #22058 (comment)

Member

justinsb commented Jun 13, 2017

This is now implemented as @kenden pointed out here: #22058 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment