It seems that dkron needs some improvements to be usable in kubernetes.
This is one of them (I’ll open an issue about the others in the main repository).
1) I added a readiness probe for the dkron server - we would like to understand whether the node is in the cluster or not.
2) podManagementPolicy: Parallel - this is necessary so that the cluster is created even if the readiness probe on the first deployed node does not pass.
3) publishNotReadyAddresses: true - so that nodes can communicate for elections
hi, @vcastellm!
It seems that dkron needs some improvements to be usable in kubernetes. This is one of them (I’ll open an issue about the others in the main repository). 1) I added a readiness probe for the dkron server - we would like to understand whether the node is in the cluster or not. 2)
podManagementPolicy: Parallel- this is necessary so that the cluster is created even if the readiness probe on the first deployed node does not pass. 3)publishNotReadyAddresses: true- so that nodes can communicate for electionsIn essence, this is a consul-like approach - statefulset и service