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
Copy file name to clipboardExpand all lines: docs/en/install.mdx
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,17 @@ Before installing, ensure you have:
32
32
- Admin permissions on the cluster
33
33
- Connectors Operator is `Ready` on ACP Operator Hub
34
34
35
+
### Pod Security Requirements for Installation \{#pod-security-requirements-for-installation}
36
+
37
+
Kubernetes enforces [Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/) (PSS) at the namespace level. The Connectors system consists of components with different privilege requirements:
38
+
39
+
| Component | Suggested Policy | Rationale |
40
+
| ---------- | ---------------- | --------- |
41
+
|**Connectors Operator**|`restricted`| Runs as a standard Kubernetes controller and does not rely on privileged capabilities. The Operator also runs correctly under the less-permissive `baseline`, but `restricted` aligns better with least-privilege practices. |
42
+
|**Other Connectors Components** (ConnectorsCore, ConnectorsGit, ConnectorsGitLab, etc.) |`privileged`| The Connectors-CSI component requires host-level access (e.g., hostPath mounts, privileged syscalls) to provide CSI driver functionality. This requirement forces the entire namespace to adopt the `privileged` policy. |
43
+
44
+
**Note**: If the namespace is configured with an insufficient policy (e.g., `restricted` or `baseline` for CSI components), the CSI driver will fail to start due to blocked privileged operations. Conversely, applying `privileged` where not needed broadens the namespace's attack surface.
45
+
35
46
### Install Connectors Operator
36
47
37
48
First, install the Connectors Operator which manages the lifecycle of all other components.
@@ -630,3 +641,24 @@ spec:
630
641
631
642
# Other configurations as needed
632
643
```
644
+
645
+
## Troubleshooting
646
+
647
+
### connectors-csi is not ready
648
+
649
+
If `daemonset/connectors-csi` is not ready, check the events of the `connectors-csi` pod.
650
+
A common error looks like:
651
+
652
+
```
653
+
Error creating: pods "connectors-csi-d4r6r" is forbidden: violates PodSecurity "baseline:latest": non-default capabilities (container "driver" must not include "SYS_ADMIN" in securityContext.capabilities.add), host namespaces (hostNetwork=true), hostPath volumes (volumes "socket-dir", "mountpoint-dir", "registration-dir") . . .
654
+
```
655
+
656
+
This means the namespace's Pod Security level is too restrictive for the CSI driver.
657
+
658
+
**Fix**
659
+
660
+
- Ensure the namespace is configured with the **`privileged`** Pod Security level.
661
+
- Update the namespace with the correct labels.
662
+
- Restart the `connectors-csi` DaemonSet.
663
+
664
+
For details, see [Pod Security Requirements for Installation](#pod-security-requirements-for-installation).
0 commit comments