Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Helm install stable/jenkins fails because of SecurityContext #160

Closed
sputnick opened this issue Nov 18, 2016 · 4 comments
Closed

Helm install stable/jenkins fails because of SecurityContext #160

sputnick opened this issue Nov 18, 2016 · 4 comments

Comments

@sputnick
Copy link

If you try to install Jenkins from stable/jenkins with Helm on Kube-Solo it fails to create its Pod with the error:
Error creating: pods "" is forbidden: pod.Spec.SecurityContext.RunAsUser is forbidden

It seems that support for SecurityContext is turned off? Saw this line kube-apiserver.service on the coreos vm.
admission_control=NamespaceLifecycle,NamespaceAutoProvision,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota

Since stable charts are what most everyone will try with Kube-Solo shouldn't this be enabled?

@rimusz
Copy link
Member

rimusz commented Nov 18, 2016

could you try to delete SecurityContextDeny https://github.com/TheNewNormal/kube-solo-osx/blob/master/src/cloud-init/user-data#L168 in ~/kube-solo/cloud-init/user-data and check if that fixes for you. if it does I will cut a new app version.
thanks

@sputnick
Copy link
Author

sputnick commented Nov 22, 2016

Hey @rimusz I deleted SecurityContextDeny and restarted the cluster and now it works to install Jenkins :). Well as long as you disable persistent storage but that's another story...

Would be great to get this built into a new release.

cheers
Eiki

@rimusz
Copy link
Member

rimusz commented Nov 22, 2016

i'm off this week, will do it when i'm back

@rimusz
Copy link
Member

rimusz commented Nov 30, 2016

fixed in https://github.com/TheNewNormal/kube-solo-osx/releases/tag/v1.0.1

@rimusz rimusz closed this as completed Nov 30, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants