README
¶
Embedded kURL cluster operator (EKCO)
EKCO is responsible for performing various operations to maintain the health of a kURL cluster.
Purge nodes
In an HA Kubernetes cluster the EKCO operator will automatically purge failed nodes that have been unreachable for more than node_unreachable_toleration (default 1h). The following steps will be taken during a purge:
- Delete the Deployment resource for the OSD from the rook-ceph namespace
- Exec into the Rook operator pod and run the command
ceph osd purge <id> - Delete the Node resource
- Remove the node from the CephCluster resource named rook-ceph in the rook-ceph namespace unless storage is managed automatically with
useAllNodes: true - (Masters only) Connect to the etcd cluster and remove the peer
- (Masters only) Remove the apiEndpoint for the node from the kubeadm-config ConfigMap in the kube-system namespace
Rook
The EKCO operator is responsible for appending nodes to the CephCluster storage.nodes setting to include the node in the list of nodes used by Ceph for storage. This operation will only append nodes. Removing nodes is done during purge.
EKCO is also responsible for adjusting the Ceph block pool, filesystem and object store replication factor up and down in accordance with the size of the cluster from min_ceph_pool_replication (default 1) to max_ceph_pool_replication (default 3).
Test manually
make docker-image
kubectl apply -k deploy/
Release
To make a new release push a tag in the format v[0-9]+\.[0-9]+\.[0-9]+(-[0-9a-z-]+)?.
git tag -a v0.1.0 -m "Release v0.1.0" && git push origin v0.1.0
Directories