currently CSI templates have hardcoded kubelet
path which will be used for mounting PVC,this
will not work if kubelet is configured to use
different path, with this PR kubelet path
can be configured for CSI.
Fixes: #3921
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
Also:
* `cluster.yaml`: spec.mgr.modules is not explicily nullable
* Removed `required: mon` in `ceph_manifests.go`
Signed-off-by: Sebastian Wagner <sebastian.wagner@suse.com>
On rare occasion, the ceph checks might not be 100% correct and the user
might decide to force an upgrade anyway.
Correctly, if we are in an upgrade, we perform `ok-to-stop` check for
each daemon, if one of them fails, we retry and eventually fail.
They are corner-cases where users would like to force the upgrade anyway.
Enhance the new CR property: "skipUpgradeChecks: true".
Closes: https://github.com/rook/rook/issues/3872
Signed-off-by: Sébastien Han <seb@redhat.com>
updated required rules for upgrading CSI from
v1.0 to v1.1 and also updated the document with
required steps
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
liveness container is deployed as part of
the provisioner pod so it has to connect to
the provisioner container and check the liveness.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
With #3626, the default value for ssl changed
from enabled to disabled, so to get SSL for
the dashboard we will need to enable it
explicitly.
Signed-off-by: Kristoffer Grönlund <kgronlund@suse.com>
Previous alert description was confusing. This makes it more
generic and user understandable.
Signed-off-by: Umanga Chapagain <chapagainumanga@gmail.com>
The upgrade was missing some final features that were added recently
such as the pod disruption budgets. The namespaced RBAC changes also
needed to have the appropriate namespaces included if they had installed
the operator in a different namespace from rook-ceph.
Signed-off-by: travisn <tnielsen@redhat.com>
rounded the value of MonLeaderChange Rate to 2 decimal points (e.g. 2.44)
previously, we had 16 decimal points (e.g. 2.4406779661016946).
This makes the alert notification more sensible and readable.
Signed-off-by: Umanga Chapagain <chapagainumanga@gmail.com>
At present, the request timeout of sidecars
are at 60s and this is a request to increase
this time out value to 150s or higher. The
higher timeout value can help to reduce the
load of our backend ceph cluster and also can
avoid throttling issues at sidecars to an extend.
Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
NFS operator.yaml example file had Windows (CRLF) line endings instead
of the Unix (LF) line endings used elsewhere. Fix this.
Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>
Add support for MachineDisruptionBudget controller and MachineLabel controller required for fencing
in OpenShift. This will ensure that machines are only fenced and OSDs are only stopped
when Ceph is in a healthy state.
Co-authored-by: Ashish Ranjan <aranjan@redhat.com>
Signed-off-by: travisn <tnielsen@redhat.com>
We can now enable via the cluster CR any manager module with a
setting under the new mgr element
mgr:
modules:
- name: pg_autoscaler
enabled: true
Co-authored-by: Sébastien Han <seb@redhat.com>
Co-authored-by: travisn <tnielsen@redhat.com>
Signed-off-by: travisn <tnielsen@redhat.com>
- Renamed MDSCOUNT to ActiveMDS & updated Description
This was to remove the confusion about what the count
is actually about (Active or Active+Standby).
Signed-off-by: Umanga Chapagain <chapagainumanga@gmail.com>
After further consideration and working with the feature for a few
weeks, the `configOverride` functionality seems to be more complexity
than is worth it for the expected benefit. Users still have the most
preferred option of setting configs in Ceph's config database using
`ceph cofig set` or the dashboard, and the override ConfigMap still
exists for fallback scenarios. The config database can still be used
by Rook for setting necessary configs, but the user has no way of
telling Rook to do so.
Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>