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.

Sign up for GitHub

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

Jump to bottom

GCE kube-up: /usr/bin/kubectl is created with mode 744 #27643

Closed
justinsb opened this issue Jun 17, 2016 · 6 comments
Closed

GCE kube-up: /usr/bin/kubectl is created with mode 744 #27643

justinsb opened this issue Jun 17, 2016 · 6 comments
Assignees
@andyzheng0831
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.3

Comments

@justinsb
Copy link
Member

justinsb commented Jun 17, 2016 •
edited by roberthbailey
Loading

This means that we have to sudo to run kubectl... It should be created with 755, not 744

justinsb@kubernetes-master ~ $ kubectl get pvc
-bash: /usr/bin/kubectl: Permission denied
justinsb@kubernetes-master ~ $ ls -l /usr/bin/kubectl
-r-xr--r-- 1 root root 55400872 Jun 17 19:44 /usr/bin/kubectl
@justinsb justinsb added this to the v1.3 milestone Jun 17, 2016
@lavalamp lavalamp added the area/release-eng Issues or PRs related to the Release Engineering subproject label Jun 18, 2016
@goltermann goltermann added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 20, 2016
@roberthbailey
Copy link
Contributor

This is a regression. It a 1.2.4 master I see

$ ls -l `which kubectl`
-rwxr-xr-x 1 root root 41225728 Jun 20 18:17 /usr/local/bin/kubectl

@roberthbailey
Copy link
Contributor

@andyzheng0831 - this is likely a result of switching the masters from containervm -> gci. Can you take a look?

@andyzheng0831
Copy link

sure, I will work on it

@vishh vishh removed their assignment Jun 21, 2016
@vishh
Copy link
Contributor

vishh commented Jun 21, 2016

I don't see any issues with the build/release pipeline. @roberthbailey Thanks for the tip!

@andyzheng0831
Copy link

I think the problem is at https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/gci/configure.sh#l142-143. For the kubelet and kubectl built in GCI image, we have the correct permission 755. I will make a change to fix it shortly

k8s-github-robot pushed a commit that referenced this issue Jun 21, 2016
Merge pull request #27740 from andyzheng0831/gci-fix
3ddff2b 
Automatic merge from submit-queue

GCI: fix kubectl permission issue #27643
@roberthbailey
Copy link
Contributor

Should this be closed now that #27740 has been merged?

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

@andyzheng0831 andyzheng0831

Labels
area/release-eng Issues or PRs related to the Release Engineering subproject priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.3
Development

No branches or pull requests
6 participants
@justinsb @lavalamp @vishh @roberthbailey @andyzheng0831 @goltermann