Kubectl apply -f common.yaml -f operator.yaml -f cluster.yaml # add other files as desired for yourconfig Deploying a second cluster \2 # driver:namespace:cluster/g" \Ĭommon.yaml operator.yaml cluster.yaml # add other files or change these as desired for your config # You need to use `apply` for all Ceph clusters after the first if you have only one Operator * \) # driver:namespace:cluster/ \1 : $ROOK_CLUSTER_NAMESPACE. \2 # driver:namespace:operator/g" \ -e "s/ \(. * \) # driver:namespace:operator/ \1 : $ROOK_OPERATOR_NAMESPACE. * \) # serviceaccount:namespace:cluster/ \1 : $ROOK_CLUSTER_NAMESPACE : \2 # serviceaccount:namespace:cluster/g" \ -e "s/ \(. * \) # serviceaccount:namespace:operator/ \1 : $ROOK_OPERATOR_NAMESPACE : \2 # serviceaccount:namespace:operator/g" \ -e "s/ \(.
*# namespace:cluster/ \1 : $ROOK_CLUSTER_NAMESPACE # namespace:cluster/g" \ -e "s/ \(. *# namespace:operator/ \1 : $ROOK_OPERATOR_NAMESPACE # namespace:operator/g" \ -e "s/ \(. This will help you manage namespaces more easily, but you should still make sure the resources areĮxport ROOK_OPERATOR_NAMESPACE = "rook-ceph" export ROOK_CLUSTER_NAMESPACE = "rook-ceph" sed -i.bak \ -e "s/ \(. To also change ROOK_OPERATOR_NAMESPACE to create a new Rook Operator for each Ceph cluster (don’tįorget to set ROOK_CURRENT_NAMESPACE_ONLY), or you can leave it at the same value for everyĬeph cluster if you only wish to have one Operator manage all Ceph clusters. ROOK_CLUSTER_NAMESPACE to tailor the manifests for additional Ceph clusters. Rook-ceph, the manifests are commented to allow for easy sed replacements.
If you wish to deploy the Rook Operator and/or Ceph clusters to namespaces other than the default If you run them in a different namespace, modify kubectl -n rook-ceph to fit The Kubernetes based examples assume Rook OSD pods are in the rook-ceph namespace. The Ceph client suite is from a Rook Toolbox container. Most of the examples make use of the ceph client command.
HOW TO RECOVER FILES IN LINUX AFTER RM HOW TO
These examples show how to perform advanced configuration tasks on your Rook
0 kommentar(er)
