miki3421 opened a new pull request, #238: URL: https://github.com/apache/openserverless-task/pull/238
Fresh installations through `build-and-test-ubuntu.sh` / `ops setup devcluster` fail to create Milvus after apache/openserverless-operator#141. That operator change reconciles NetworkPolicies, but setup applies its own bootstrap Role from `setup/kubernetes/roles/operator-roles.yaml`, which currently grants access only to ingresses in `networking.k8s.io`. The operator receives `Forbidden` when applying `openserverless-etcd-isolation`. This interrupts etcd setup before its readiness wait, prevents provisioning the Milvus technical account, and leaves setup waiting for a Milvus pod that was never created. Add `networkpolicies` to the existing networking rule. Its verbs match those already included in the operator's Role by apache/openserverless-operator#141, and permission remains scoped to the `openserverless` namespace. Validation: - Parsed both YAML documents successfully. - Confirmed the NetworkPolicy verbs match the operator Role at `e26b21b53c87b67d5b58911a492d72b2f5405ac8`. - Compared parsed documents: all other permissions, metadata and the RoleBinding are unchanged. - `git diff --check` passed; exactly one file and one line changed. - The original failure was observed on a fresh Kind installation. No live installation was modified or rerun for this patch. The separate operator issue that reports Milvus `on` after a failed creation is outside this minimal bootstrap-permission fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
