We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I am trying to install Cilium on OpenShift 4.15 with BGP Control plan enabled in the OLM Manifest:
bgpControlPlane: enabled: true
This result in the Operator to fail with this error message:
2024-03-20T03:33:39Z ERROR helm.controller Release failed { "namespace": "cilium", "name": "cilium", "apiVersion": "cilium.io/v1alpha1", "kind": "CiliumConfig", "release": "cilium", "error": "failed to install release: 2 errors occurred:\n\t* roles.rbac.authorization.k8s.io \"cilium-bgp-control-plane-secrets\" is forbidden: user \"system:serviceaccount:cilium:cilium-olm\" (groups=[\"system:serviceaccounts\" \"system:serviceaccounts:cilium\" \"system:authenticated\"]) is attempting to grant RBAC permissions not currently held:\n{APIGroups:[\"\"], Resources:[\"secrets\"], Verbs:[\"get\" \"list\" \"watch\"]}\n\t* roles.rbac.authorization.k8s.io \"cilium-bgp-control-plane-secrets\" not found\n\n", }
This seems a similar issue as reported in #89 as a work around I have edited cluster-network-06-cilium-00009-cilium-cilium-clusterrole.yaml and added:
cluster-network-06-cilium-00009-cilium-cilium-clusterrole.yaml
- apiGroups: - "" resources: - secrets verbs: - get - list - watch
This seems to have fixed the issue
The text was updated successfully, but these errors were encountered:
Using this should stop the error message
bgpControlPlane: enabled: true secretsNamespace: name: cilium create: false
Sorry, something went wrong.
No branches or pull requests
Hello,
I am trying to install Cilium on OpenShift 4.15 with BGP Control plan enabled in the OLM Manifest:
This result in the Operator to fail with this error message:
This seems a similar issue as reported in #89 as a work around I have edited
cluster-network-06-cilium-00009-cilium-cilium-clusterrole.yaml
and added:This seems to have fixed the issue
The text was updated successfully, but these errors were encountered: