You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
###FsGroup policy not propagated from pod security context
133
+
## FsGroup policy not propagated from pod security context
134
134
135
135
If your fsGroup is not being applied on the files in your volume.
136
136
@@ -183,6 +183,21 @@ spec:
183
183
```
184
184
`File` - Indicates that the CSI volume driver supports volume ownership and permission change via fsGroup, and Kubernetes may use fsGroup to change permissions and ownership of the volume to match user requested fsGroup in the pod's SecurityPolicy regardless of fstype or access mode.
185
185
186
+
## Calico-node pods fail readiness health checks when oci-fss-utils is installed on node
187
+
188
+
If you are using Calico CNI, the following error is thrown by the Calico daemonset pods that are scheduled on the node which has oci-fss-utils package installed:
189
+
```
190
+
Readiness probe failed: 2023-10-12 08:51:08.172 [INFO][346] confd/health.go 180: Number of node(s) with BGP peering established = 0 calico/node is not ready: BIRD is not ready: BGP not established with 10.0.0.5,10.0.76.88,10.0.66.239
191
+
```
192
+
193
+
### Solution:
194
+
195
+
Add the following env setting to the calico-node container in the calico-node daemonset manifest.
0 commit comments