The toolbox was not respecting the rook-config-override ConfigMap,
resulting in a minimal ceph.conf with only mon_host and keyring settings.
This made it difficult to run diagnostic commands that require custom
configuration parameters.
This change mounts the rook-config-override ConfigMap in all toolbox
variants and merges its contents into the generated ceph.conf. The
merge happens after writing the base config with mon endpoints, and
is re-applied whenever mon endpoints change.
The toolbox now has consistent behavior with other Rook-managed Ceph
daemons (mon, mgr, osd, mds, rgw) which already respect config overrides.
Signed-off-by: Matthew N. Heler <matthew.heler@hotmail.com>
(cherry picked from commit 9570d141de)
Correct the names used for controller plugin and node plugin resource
setting
Signed-off-by: Steve Wills <steve@mouf.net>
(cherry picked from commit 604226770e)
If the ceph status is "active+lean+snaptrimp" or
"ative+clean+snatrip_wait" , the the PDB controller should treat this
ceph staus as healthy and don't block the node drain
Signed-off-by: Santosh Pillai <sapillai@redhat.com>
(cherry picked from commit c0eb34815f)
if the filesystem is just created and getting the status
updated svg controller can still go and proceed to
check the filesystem status
If the filesystem status is empty we should retry instead of
proceeding further
Signed-off-by: parth-gr <partharora1010@gmail.com>
(cherry picked from commit fb7226698b)
if the pool is just created and getting the status
updated rn controller can still go and proceed to
check the pool status
If the pool status is empty we should retry instead of
proceeding further
Signed-off-by: parth-gr <partharora1010@gmail.com>
(cherry picked from commit 7ef4b4849c)
Signed-off-by: parth-gr <partharora1010@gmail.com>
currently, in SVG crd while updating status we don't have retryOnConflicts
similar to other CRD, this commit add the retryOnConflicts.
Signed-off-by: subhamkrai <srai@redhat.com>
(cherry picked from commit e9d5efb3e1)
currently, in RNS crd while updating status we don't
have retryOnConflicts, similar to other CRD due to
this RNS status was not updated succesfully and to
fix this we have restart the rook operator pod.
Signed-off-by: subhamkrai <srai@redhat.com>
(cherry picked from commit c8ee7305d4)
currently the device class label was added to the osd pod,
we need the device class label on prepare pod,
so to spread across prpeare pods evenly among the faiure domains
per device class
Signed-off-by: parth-gr <partharora1010@gmail.com>
(cherry picked from commit 4fcdfaad1f)
Fixed a syntax error caused by incorrect quotation parsing in the importClusterID function of import-external-cluster.sh, and updated the output message shown while waiting for the SubVolumeGroup CR to be created.
Signed-off-by: GanghyeonSeo <sgh000109@gmail.com>
(cherry picked from commit f9acdab146)
Document how to migrate an application with a dynamic
PV rather than a static PV, since static PVs have limitations
such as not supporting snapshots and clones.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 4cd6416dab)
Applications can be migrated between clusters that are
connecting to the same external Ceph cluster.
This is done with a static PV that can be mounted
by the application across the clusters.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit dba69aab0a)
Noticed two small typos when reading the documentation on object stores.
I also noticed that the lack of a whitespace in the creating a user
example affects the syntax highlighting.
Signed-off-by: Richard Goodman <richardg@brandwatch.com>
(cherry picked from commit f833c549bb)
Add optinal hostnetwork field for Ceph Mgr to control whether the
mgr pods to run in host network. If unset, this defaults to
cluster level Network.HostNetwork value. This particulary useful
when user wants to restrict ceph mgr pod from exposing metrics
port in all host interfaces.
Signed-off-by: Sunnatillo <sunnat.samadov@est.tech>
(cherry picked from commit b9a4685f65)
Update a broken link due to the Kubernetes in-tree NFS driver being
archived/deprecated. Update the link to refer to the latest NFS CSI
driver.
Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>
(cherry picked from commit 55a4c63d31)
Wait for the mon-canary pods to be terminated before starting the actual
mons. When topology spread constraints are added to evenly spread the
mons, then pod-anti affinity does not allow mons to be created on the
same node where other mons are running, this also includes the
mon-canary pods. We delete the mon-canary pods and then start the actual
mon pods. Sometimes the termination of the canary pods might take more
time, so schedular won't schedular mon pods on that node.
Signed-off-by: Santosh Pillai <sapillai@redhat.com>
(cherry picked from commit 3137a857df)