-
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
add label to kube-proxy #617
Conversation
signed cla/linuxfoundation |
Looks good. Wondering though - does the k8s-app do anything special? I'm not aware of any special significance, so I'd like to understand why you want the label, so we can be sure to add it to other things in future! |
I added to keep the same as kube-up. I'm using to validate that the cluster has been provisioned correctly with the number of nodes. Having a label on all pods makes it easier to validate :) |
@ajohnstone |
I've seen instances whereby kube-proxy was failing say 1/5 pods. I've wrote tests, that verify the health of the cluster that my colleagues can easily run. The above simply makes it easy to query for kube-proxy. E.g.
Otherwise you have to grep for the name. Ideally all applications should be easy to query with relevant labels. |
|
@shamil production nope. |
I would say kops is our best bet for production readiness. I feel we're well beyond where kube-up is/was. Not tool is 100% out of the box for everyone, and I would like to see #428 , but IMO we should be promoting kops, and identifying areas where it is not "production ready". This seems like another PR that gets us closer @ajohnstone - thank you! LGTM |
No description provided.