-
Notifications
You must be signed in to change notification settings - Fork 542
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
The operator cannot be installed normally in a cluster with psp #2066
Comments
joelanford
added
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
and removed
kind/bug
Categorizes issue or PR as related to a bug.
labels
Apr 1, 2021
A potential solution is to create a separate ServiceAccount for the new CatalogSource that is created in that namespace instead of using the |
dinhxuanvu
removed
the
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
label
Aug 19, 2021
joelanford
removed
the
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
label
Aug 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
The k8s cluster opens the psp policy, and the operator installation through olm will fail. because of the job in the namespace
olm
use default serviceaccount.related issue
What did you do?
A clear and concise description of the steps you took (or insert a code snippet).
filepath: quickstart
What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
etce operator can be installed normally.
What did you see instead? Under which circumstances?
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedCreate 6m58s (x15 over 65m) job-controller Error creating: pods "fe3359f072ef3976d6cf0d56c20a540531916356d88290cd72c0b5916672ca0-" is forbidden: unable to validate against any pod security policy: []
Environment
0.17.0
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"37996579a3bc0da0dad9ed07929115d8a6c4b28c", GitTreeState:"clean", BuildDate:"2020-08-18T10:49:04Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"719f645b9670949cde39510176c1a7a61c4039a0", GitTreeState:"clean", BuildDate:"2020-08-18T09:53:48Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Possible Solution
olm
sa for the joboperator-lifecycle-manager/pkg/controller/bundle/bundle_unpacker.go
Line 68 in 5eb1fa6
The text was updated successfully, but these errors were encountered: