The docs failed to publish with the mkdocs.yml in the root
folder instead of where the docs are being built.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The requirements_docs.txt is expected by the build.docs
build target in build/release. Since the txt file was at
the root of the repo, the build was failing to be pubished
when it didn't find the file in build/release.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The Rook and Ceph teams settled on using slashes to separate Rook
telemetry items into a hierarchy in https://github.com/rook/rook/pull/10254.
Rename the config-key used to `rook/version`, and create a `telemetry`
package to define the telemetry key constants.
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
The ceph upgrade guide is factored out into a separate document
to help simplify the flow and make the different types of
upgrades more easily discoverable.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Deploying a custom CSI image is more of a standalone topic
under the CSI configuration docs. There is no need for the
upgrade guide to have the details about CSI images.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
If the monitoring settings are not specified in the values.yaml,
avoid a helm chart install error by skipping the monitoring
section of the cephcluster CR altogether.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The cephcluster CR monitoring schema should be honored. The helm
chart was creating extra values that didn't match the schema by
copying the values such as createPrometheusRules that are only
used for template evaluation. Now only the monitoring values
from the schema will be added to the template.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The `watch` verb is not required for the csi-snapshotter sidecar
to function, removing it from the deployment
Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
Ceph upstream telemetry (which Rook users could optionally enable via
Ceph CLI or Dashboard) does not easily identify if a cluster is managed
by Rook. Identifying Rook clusters is possible only if users also enable
the rook mgr module, which is optional and not often used.
To get better upstream insights into Ceph clusters managed by Rook, set
a new 'rook-version' field in Ceph's generic k/v store. This field can
be used to determine if a cluster is managed by Rook by its presence.
It additionally provides information about the Rook version used to
manage the cluster, which is another piece of potentially useful
information.
Regarding Ceph cluster identification via telemetry:
Ceph telemetry is anonymous and uses a different ID from the Ceph
cluster ID. Identifying the Rook version in telemetry does not add
directly identifying information. Therefore, there should be little
risk that adding the Rook version field will decrease anonymity of Ceph
clusters via telemetry.
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
Now rgw can be pass by FQDN too,
to avoid problems where it is required
The format should be similar to
Ip(<IP>:<PORT> format), <FQDN>:<PORT> format
Signed-off-by: parth-gr <paarora@redhat.com>
The startup probe for the OSD has been too aggressive to kill the OSD
in case the OSD is taking some time to start. The OSD may be self-optimizing,
scrubbing, or some other internal operation before it is ready to start.
Rather than disable the startup probe completely, the default is now
to retry for two hours in case the OSD is performing those operations.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Currently it was mention we are updating the csi-user
But more precisely we go and update the keyrings
which auto update users so replacing it
Signed-off-by: parth-gr <paarora@redhat.com>
The ceph-external-cluster-details-exporter.py
generates the json output even with
rgw-endpoint IP from different cluster
Added a check validate_rgw_endpoint which will validate
the above rgw_endpoint Ip by matching the cluster fsid
Signed-off-by: parth-gr <paarora@redhat.com>
We don't need to run any `cp` command since a destination path already
exists. Using `--no-clobber` is not needed and it results in a noop
anyways.
Instead, let's print the reason why we exit the container.
Signed-off-by: Sébastien Han <seb@redhat.com>
This commit adds psp RoleBindings to rook-ceph-rgw role and
rook-ceph-purge-osd role. Without this commit, I cannot perform
rook-ceph-purge-osd job on PSP-enabled cluster.
Signed-off-by: Yuichiro Ueno <ueno@preferred.jp>
Travis Nielsen
Alexander Trost
Blaine Gardner
Humble Chirammal
Madhu Rajanna
Sébastien Han
Sean Johnson
Yuval Manor
parth-gr
Yuichiro Ueno