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
> - `address`: Should point to the service created in step 2, replace `<service-name>`, `<driver-namespace>`, and `<service-port>` with your actual values from step 2
94
-
> - `audience`: Recommended to use the CSI driver name for consistency
95
-
> - `caCert`: Base64-encoded CA certificate bundle
96
-
97
-
5. Provide the TLS secret required for the `external-snapshot-metadata` sidecar as a volume mount in the RBD driver CR.
78
+
This is the trigger for sidecar deployment: the operator deploys the
79
+
`external-snapshot-metadata`sidecar whenever it finds a volume named `tls-key`
80
+
in `spec.controllerPlugin.volumes` of an RBD Driver CR.
98
81
99
82
**Example:**
100
83
@@ -110,25 +93,43 @@ Users need to perform the following manual setup:
110
93
volumes:
111
94
- mount:
112
95
mountPath: /tmp/certificates # Must be /tmp/certificates - required by sidecar
113
-
name: tls-key
96
+
name: tls-key
114
97
volume:
115
98
name: tls-key # Must be "tls-key"
116
99
secret:
117
-
secretName: snapshot-metadata-tls # The TLS secret name
100
+
secretName: snapshot-metadata-tls # The TLS secret name from step 3
118
101
```
119
102
120
103
> **Note:**
121
104
> - **mountPath must be `/tmp/certificates`**: This path is required by the snapshot metadata sidecar to locate TLS certificates.
122
-
> - **Volume name and mount name must be `tls-key`**: The operator specifically filters for volumes with this exact name to mount in the snapshot-metadata sidecar container.
105
+
> - **Volume name and mount name must be `tls-key`**: The operator specifically looks for this name to deploy the sidecar.
123
106
> - Replace `<driver-name>` with your RBD driver name (e.g., `rbd.csi.ceph.com`)
124
107
> - Replace `<driver-namespace>` with the namespace where your RBD driver is deployed
125
108
109
+
5. Create a SnapshotMetadataService CR for the RBD driver so backup vendors can
110
+
discover the sidecar endpoint. The name of this CR must match the RBD driver CR name.
> - `address`: Should point to the service created in step 2, replace `<service-name>`, `<driver-namespace>`, and `<service-port>` with your actual values from step 2
127
+
> - `audience`: Recommended to use the CSI driver name for consistency
128
+
> - `caCert`: Base64-encoded CA certificate bundle
129
+
126
130
## Ceph-CSI Operator Responsibilities
127
131
128
132
The operator will perform the following actions for the RBD controller plugin deployment:
129
133
130
-
- Check for the existence of the SnapshotMetadataService CR (name must be the same as the RBD driver CR)
131
-
- Check for the volume of type SecretVolumeSource (name must be the same as the RBD driver CR)
132
-
133
-
> ⚠️ **Note**: If the SnapshotMetadataService CR is created after adding the volume configuration
134
-
> in the RBD driver CR, the ceph-csi-operator pod needs to be restarted manually.
134
+
- Check for a volume named `tls-key` in `spec.controllerPlugin.volumes` of the RBD Driver CR
135
+
- If present, inject the `csi-snapshot-metadata` sidecar into the controller plugin deployment and mount the TLS certificates at `/tmp/certificates`
0 commit comments