The controller for disruption budgets is verbose at cluster creation
when the cluster is not yet created, which generates a lot of noise
in the log that makes the cluster look unhealthy. This is an expected
condition, so we can change this logging to debug level.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
We discovered the hard way that configuration through the environment
does not work if this ConfigMap is not present altogether. Document this
as a common issue.
Closes#9806.
Signed-off-by: Matthias Rampke <matthias@rampke.de>
To ensure the mgr is not the single point of failure, the mgr
daemon count is now set to 2 by default in the cluster examples.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The PR checklist has a couple links that were outdated
and some other items that are generally not necessary to
consider in every PR. Now the checklist is more concise
and links are updated.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Currently, the admin/user can configure the ceph.conf
for daemon pods using https://rook.io/docs/rook/v1.7/
ceph-advanced-configuration.html#custom-cephconf-settings.
This the above custom ceph.conf is only for ceph pods.
the support to provide constom ceph.conf for cephcsi
is added in cephcsi PR 2476
This PR adds the support to create/update
ceph.conf for csi pods.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
The latest ceph image should be used for the base of
the rook image to pick up the latest security releases.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The osd destroy command leaves the osd id in use instead
of fully purging the osd id. If the osd id is not also
removed, it gives the impression that there is still
something that needs to be cleaned up from the old osd.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The purge job is intended to clean up all the resources
related to an OSD that is to be removed. An OSD with
a metadata, wal, and data PVC was only cleaning up the
data PVC. Now the metadata and wal PVCs will also be
cleaned up.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
If the filesystem is in a bad state such as never being
created successfully in the first place, the filesystem
removal will continuously fail and prevent the CR from
being removed. Thus, we treat the filesystem removal
as a best effort and log the issue instead of failing
the uninstall reconcile.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The operator and toolbox pods were not configurable for
their priority class in the helm chart. Now the settings
are exposed in the values.yaml.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Added unit test for probes changes and
did re-naming of liveness probes file
as it will contain multiple types of probes
Signed-off-by: parth-gr <paarora@redhat.com>
Based on my testing with the guide above,
the original value in the sample code here:
`VAULT_BACKEND_PATH: rook/ver1`
...did not work and resulted in
a Vault path error when Rook attempted
to provision the OSD filesystem.
When I simplified it to:
`VAULT_BACKEND_PATH: rook`
... then it worked.
I also took the opportunity to add
a comment/clarification about the `VAULT_ADDR` URL.
Co-authored-by: Shahak Nagiel <snagiel@yahoo.com>
Signed-off-by: parth-gr <paarora@redhat.com>
Two test jobs were collecting artifacts to the same artifact name, which
can cause race conditions and failures to upload artifacts.
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
The docs have links pointing /design directory in the codebase which
hidden in https://rook.io so change them to rook github repo links.
Fixes: #9768
Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
If Rook is run on a developer machine, devices may accidentally
be consumed by rook and cause data loss.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
currently if multisite is not configured Rook sets values for
zone/zonegroup/realm as object store name which is only valid for
internal ceph object store. This may not exists for rgw running in
external cluster.
Signed-off-by: Jiffin Tony Thottan <thottanjiffin@gmail.com>