Skip to content

kserve: set storage initializer security context #3527

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.

Sign up for GitHub

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

Draft
danish9039 wants to merge 1 commit into
base: master
Choose a base branch
from
+19 −0
Draft

kserve: set storage initializer security context #3527

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions applications/kserve/kserve/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,25 @@ patches:
seccompProfile:
type: RuntimeDefault

# Make the KServe storage initializer init container restricted-PSS compatible
- patch: |
apiVersion: serving.kserve.io/v1alpha1
kind: ClusterStorageContainer
metadata:
name: default
namespace: kubeflow
spec:
container:
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
runAsNonRoot: true
runAsUser: 1000
seccompProfile:
type: RuntimeDefault

# Delete ALL insecure LLMInferenceServiceConfig resources
# IPC_LOCK, SYS_RAWIO, NET_RAW capabilities, runAsNonRoot: false
# Ref: https://github.com/kubeflow/community-distribution/issues/3290
Expand Down
Loading