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

kubevirt.io demo doesn't indicate need to use system:admin for oc commands #164

Closed
markllama opened this issue Nov 16, 2018 · 2 comments
Closed

Comments

@markllama
Copy link
Contributor

The kubevirt.io try-me for minikube/minishift has oc commands that require use of the system/admin user. There is no note to that effect in the text.

http://kubevirt.io/get_kubevirt/

Deploying KubeVirt on OpenShift Origin
On OpenShift Origin, the following SCCs need to be added prior kubevirt.yaml deployment:

$ oc adm policy add-scc-to-user privileged system:serviceaccount:kube-system:kubevirt-privileged
$ oc adm policy add-scc-to-user privileged system:serviceaccount:kube-system:kubevirt-controller
$ oc adm policy add-scc-to-user privileged system:serviceaccount:kube-system:kubevirt-apiserver

$ export VERSION=v0.8.0
$ oc apply -f https://github.com/kubevirt/kubevirt/releases/download/${VERSION}/kubevirt.yaml

@markllama
Copy link
Contributor Author

Resolved for minikube and minishift. AWS and GCE images are still out of date.

@karmab
Copy link
Contributor

karmab commented Nov 19, 2018

addressed in #166 with an explicit login as system:admin prior to running the scc related commands although arguably, both oc and kubectl commands from the getting started require enough privileges for kubevirt deployment to actually happen

@karmab karmab closed this as completed Nov 21, 2018
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

No branches or pull requests

2 participants