extra_binds has to be on same level as extra_args. Currently it will interpreted as another argument resuling in kubelet being called with the non-existent argument "--extraBinds=/usr/libexec/kubernetes/kubelet-plugins/volume/exec:/usr/libexec/kubernetes/kubelet-plugins/volume/exec" leading to a crash/reboot-loop of the kubelet.
Signed-off-by: Maximilian Heinrich <maximilian.heinrich@esono.de>
The namespace referred to by the prose text in the "Create a Rook Cluster" when creating the cluster was incorrect and did not match the example below, which was correct.
Signed-off-by: John Mulligan <jmulligan@redhat.com>
Add steps to clean the disks on a node after Rook has been removed so
that they are in a usable state again.
Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>
In our 0.9 rook deployment, the `app` label assigned to the operator is `rook-ceph-operator` which was incorrectly speficied in the documentation:
```
$ kubectl describe pod/rook-ceph-operator-765bcd58b-6rr2q | grep app=
Labels: app=rook-ceph-operator
```
Signed-off-by: Antoine Beaupré <anarcat@debian.org>
This allows multiple object stores to be in the same namespace and
to be selected separately from each other.
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
Based on discussion in issue #2411, clarify Rook and Ceph's behavior
around allowing the user to create a cluster where data replication
cannot tolerate the cluster's failure domain safely.
Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>
It appears this reference to 'rook' was inadvertently not updated
to 'rook-ceph' when multiple backend storage system support was
added. Both the surrounding documentation and code seem to support
the idea that this is the correct value.
Signed-off-by: James E. Blair <jeblair@redhat.com>
New configurational option enables flexible choice for write I/O
to allow configurable trades between performance, reliability and consistency.
This also fixes bcache mis-configuration.
Fixes#2367
Signed-off-by: Dmitry Yusupov <dmitry@nexenta.com>
The command `kubectl delete -n rook-ceph pool replicapool` returns the error `error: the server doesn't have a resource type "pool"`. The actual resource type is `cephblockpools.ceph.rook.io`.
Signed-off-by: Earl C. Ruby III <earlruby@users.noreply.github.com>
The modified links are on the page
https://rook.io/docs/rook/v0.9/k8s-pre-reqs.html
but are broken when clicked, because they are relative. This change makes them absolute so they work from both GitHub and the rook.io site.
Signed-off-by: Ryan Goodfellow <rgoodfel@isi.edu>