my-rook-config

Files

T

Travis Nielsen 95171c682b ceph: continue with orchestration if a single mon pod fails to start

If the cluster has previously been initialized and the operator
is restarted, the operator needs to perform the first orchestration
to confirm basic cluster health, then start watching for CR events.
If there was a single mon pod in a failed or pending pod state, the
orchestration was blocked even if just one mon was in this state.

The scenario is when a node is lost and a mon and the operator happen
to be running on that node. The operator will restart, but the mon
will not restart because it is tied to the node that died (unless running
on a PVC). The mon would remain in a pending state while attempting
to schedule on the node that is down indefinitely and the operator would
be blocked indefinitely. Now we will just log the error and attempt
to continue.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

2019-10-30 08:24:18 -06:00

config_test.go

ceph: rework csi keys and secrets

2019-10-22 15:14:28 +02:00

config.go

ceph: rework csi keys and secrets

2019-10-22 15:14:28 +02:00

endpoint_test.go

ceph: refactor csi related code into a new file in csi package

2019-08-12 16:41:26 -04:00

endpoint.go

ceph: refactor csi related code into a new file in csi package