Skip to content
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

Merged
merged 1 commit into from
Oct 11, 2016
Merged

Conversation

ajohnstone
Copy link
Contributor

No description provided.

@ajohnstone
Copy link
Contributor Author

signed cla/linuxfoundation

@justinsb
Copy link
Member

justinsb commented Oct 9, 2016

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!

@ajohnstone
Copy link
Contributor Author

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 :)

@chrislovecnm
Copy link
Contributor

@ajohnstone kube-up.sh is depreciated, what are you trying to validate? Wonder if we can do this another way. I would like to model more of what kubeadm is doing now since we may integrate that in eventually.

@ajohnstone
Copy link
Contributor Author

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.

bats tests/
 ✗ kube-proxy pods
   (from function `values_equal' in file tests/../helpers.bash, line 37,
    in test file tests/pod_counts.bats, line 63)
     `values_equal ${KUBE_PROXY_DESIRED} ${KUBE_PROXY_CURRENT};' failed
   KUBE_PROXY_DESIRED: 8 KUBE_PROXY_CURRENT: 0

Otherwise you have to grep for the name. kubectl --namespace=kube-system get pods -o name | grep -E 'pod/kube-proxy-.*'

Ideally all applications should be easy to query with relevant labels.

@shamil
Copy link
Contributor

shamil commented Oct 10, 2016

kube-up.sh is depreciated
@chrislovecnm do we have production grade replacement?

@chrislovecnm
Copy link
Contributor

@shamil production nope. kubeadm is scheduled but just released in 1.4. We need to discuss as a group when, if, and we are going to use kubeadm

@justinsb
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants