Describe the Bug
When deploying the Milvus Operator in secure Kubernetes environments, deployments fail. This occurs because the securityContext of the component is not inherited by its configuration init container, causing the admission controller to reject the pod.
Importance
This is currently a blocker for our organization's security compliance audit, preventing us from running Milvus in production.
Existing Solution
There is already an approved PR that fixes this exact issue: #464.
The PR is approved but appears to be stuck under a do-not-merge/hold label. Could a maintainer please help lift the hold and merge the PR so we can resolve this block?
Describe the Bug
When deploying the Milvus Operator in secure Kubernetes environments, deployments fail. This occurs because the
securityContextof the component is not inherited by its configuration init container, causing the admission controller to reject the pod.Importance
This is currently a blocker for our organization's security compliance audit, preventing us from running Milvus in production.
Existing Solution
There is already an approved PR that fixes this exact issue: #464.
The PR is approved but appears to be stuck under a
do-not-merge/holdlabel. Could a maintainer please help lift the hold and merge the PR so we can resolve this block?