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

OpenShift environment - Kube-Notary pod runs into permission error #12

Open
opvizordz opened this issue Oct 23, 2019 · 2 comments
Open
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@opvizordz
Copy link

I deployed Kube-Notary into our OpenShift environment using the deployment scripts in this repo (kubernetes/kube-notary/templates):

Step by step I ran:

oc login -u system:admin
 kubectl apply -f serviceaccount.yaml
 oc adm policy add-scc-to-user privileged -z kube-notary
 kubectl apply -f role.yaml
 kubectl apply -f rolebinding.yaml
 kubectl apply -f service.yaml
 kubectl apply -f configmap.yaml
 kubectl apply -f deployment.yaml

When checking the logs of the kube-notary pod:

kubectl get  pods | grep kube-notary
kubectl logs kube-notary-...

I see the following errors:

Error getting pods: pods is forbidden: User \"system:serviceaccount:test:kube-notary\" cannot list pods at the cluster scope: no RBAC policy matched"

No data is being collected.

@opvizordz
Copy link
Author

I actually solved it myself ... OpenShift is automatically pointing to the project namespace when running kubectl.
The file rolebinding.yaml points to namespace default. In my case the project was not in the namespace default but test.

Changing the namespace to test, did the trick

@leogr leogr added the documentation Improvements or additions to documentation label Oct 23, 2019
@leogr
Copy link
Contributor

leogr commented Oct 23, 2019

It just needs to be well documented. I'll close the issue when done.

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

No branches or pull requests

2 participants