As a Kubernetes Administrator, you can use this information to configure the Ceph-CSI driver for use with IBM Storage Ceph Block Devices (RBD) on your cluster.
Before you begin
- Be sure that the Ceph-CSI driver and relevant YAML files, provided by IBM Sales are installed.
- Ensure connectivity between Kubernetes and the Ceph cluster exists by using ping or telnet.
Procedure
Update the
values.yaml file with the relevant values for
Ceph-CSI driver configuration.
Important: Keep only the required changes.
-
Update all nodeplugin.image.* parameters for the Ceph-CSI driver.
Use the parameter values listed in
Table 1 to configure the
Ceph-CSI driver.
Table 1. Ceph-CSI driver nodeplugin.image.* parameters
| Parameter |
Value |
| nodeplugin.plugin.image.repository |
cp.icr.io/cp/ibm-ceph/cephcsi |
| nodeplugin.plugin.image.tag |
|
| nodeplugin.plugin.image.pullPolicy |
Always |
For example, to update with Helm:
helm install --set nodeplugin.plugin.image.repository=cp.icr.io/cp/ibm-ceph/cephcsi --set nodeplugin.plugin.image.tag= --set nodeplugin.plugin.image.pullPolicy=IfNotPresent
-
Update all provisioner.provisioner.image.* parameters for the relevant kubernetes-csi container-images from the Kubernetes vendor.
- provisioner.provisioner.image.repository
- provisioner.provisioner.image.tag
- provisioner.provisioner.image.pullPolicy
- provisioner.provisioner.image.extraArgs
For example, to update with Helm:
helm install --set provisioner.provisioner.image.repository=registry.k8s.io/sig-storage/csi-provisioner --set provisioner.provisioner.image.tag=v5.1.0 --set provisioner.provisioner.image.pullPolicy=IfNotPresent --set provisioner.provisioner.image.extraArgs=[]
-
Update the required clusterID and monitor information, provided by the Ceph administrator.
csiConfig:
- clusterID: "79179d9d-98d8-4976-ab2e-58635caa7235"
monitors:
- "10.85.8.118:6789"
- "10.85.8.123:6789"
- "10.85.8.124:6789"
provisioner:
name: provisioner
replicaCount: 2
- Optional:
Update any other needed parameters.
-
Verify that all Ceph monitors are reachable from the cluster, by pinging the monitors.
For example,
ping 10.85.8.118