Important information you should know prior to using Rook Ceph in DKP
The Ceph instance installed by DKP is intended only for use by the logging stack and
velero platform applications.
If you have an instance of Ceph that is managed outside of the DKP lifecycle, see Bring Your Own Storage to DKP Clusters.
If you do not plan on using any of the logging stack components such as
velero for backups, then you do not need Rook Ceph for your installation and you can disable it by adding the following to your installer config file:
apiVersion: config.kommander.mesosphere.io/v1alpha1 kind: Installation apps: ... ... grafana-loki: enabled: false ... rook-ceph: enabled: false rook-ceph-cluster: enabled: false ... velero: enabled: false ...
You must enable
rook-ceph-cluster if any of the following is true:
velerois enabled. If you applied config overrides for
veleroto use a storage that is external to your cluster, then you do not need Ceph to be installed.
Disabling Ceph during Upgrades (from DKP 2.3.x)
Up until DKP 2.3.x,
MinIO was used as the default blob storage for DKP components. This has been replaced by Ceph from
2.4.x, therefore when you upgrade from
2.3.x -> 2.4.x, Ceph is automatically installed if any of the following are true:
minio-operatorwas installed (used by logging stack).
velerowas installed (used for backups).
However, If you did not have
minio-operator installed in
2.3.x and instead had configured
velero to work with an external cloud storage such as
Amazon S3 or
Azure Blob Storage, then you do not need
rook-ceph-cluster post upgrade.
To explicitly disable installing these apps during upgrade, specify the following in the command line, then run the following command:
dkp upgrade kommander --disable-appdeployments rook-ceph,rook-ceph-cluster
The command above fails if
minio-operator is installed as you cannot disable Ceph installation if minio-operator is installed.