-
Notifications
You must be signed in to change notification settings - Fork 835
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
Allow seldon manager to run as non-root #2631
Comments
Makes sense, we need to add a section like https://github.com/helm/charts/blob/master/stable/ambassador/templates/deployment.yaml#L49 Not quite as simple as it sounds as our helm chart is generated from kustomize using python code |
@ryandawsonuk Thank you for your update As this is a blocker for us to proceed with seldon deployment, can the fix be a part of the next release? |
@ryandawsonuk Any updates? |
Hey @mo-saeed, we've already started to cut the 1.5 release. However, we could include this for 1.6. Given that you've already started to look into this locally, would you be willing to contribute a PR with the required changes? |
Hi @adriangonz Thanks for the updates, I hoped to have such an important fix in 1.5. Can you please provide documentation on how to use this script so I can create the pull request, the change for me sounds to be easy which is adding this
after this line https://github.com/SeldonIO/seldon-core/blob/master/operator/helm/split_resources.py#L156 But I dunno how to test this properly and I can't find any documentation. Thanks |
I agree we should document these steps in a developer section. |
@cliveseldon @adriangonz Pull request created, please have a look. There were also some other changes caused by the build process, I am not sure if it can be avoided or it's ok to have it. |
The PR that fixed this was incorrect
|
reverted in #2752 |
And why was it reverted, instead of only fixing the issue? I don't get the first point, coz nth was changed regarding the webhook port. for the second point, how can that be configured properly in this python script? |
The install is broken in master so have reverted. We can put the fix back in with corrections. Will need to look what we do for openshift where we change the webhook port to a non-root value such as 4443 and also ensure the value is correctly set. |
Yes agreed. The issue was it was setting it as a string when it needs to be an int. |
Describe the bug
the helm installation of seldon-core-operator failed coz
seldon-controller-manager
fails to start with this errorSo it seems that the image tries to run as a root and our pod security policy dissallow that.
Please have a look into this thread https://seldondev.slack.com/archives/CSVSD5S75/p1605193934193300
To reproduce
Expected behaviour
Installation completes successfully and all pods should run not with root user.
Environment
K8s cluster- AKS v1.18
seldon-core-operator version 1.4.0
The text was updated successfully, but these errors were encountered: