Editing Rook Storage for Kubernetes (section)

=== Rook Operator ===
Creating the Rook Operator simply requires loading two manifests with no customization.  First, set up the namespace and all the roles, bindings, and support definitions:

 kubectl create -f crds.yaml -f common.yaml

Then create the rook operator itself and wait for it to settle into a Running state.

 kubectl create -f operator.yaml

The Rook Operator manages the entire activity of the storage enterprise, so tailing the log in a separate window will be useful should any problems arise:

 kubectl get pods -n rook-ceph
 kubectl logs -f -n rook-ceph <pod name>

The beauty of the operator concept in kubernetes is that it is capable of accomplishing practically anything that can be done from the command line -- all in response to what it sees in the cluster configuration.  In this case, the operator looks for the Custom Resource Definition (CRD) that defines a Ceph Cluster -- with the parameters set to define what that ceph cluster looks like.  If it sees that a new cluster needs to be created, it will do all the steps needed to create and provision the ceph cluster as specified.  If interfacing with an external ceph cluster is required, it takes the provided credentials and identifiers and connects to that cluster to get the storage service.