Add Kubernetes clustering with prometheus output docs #568
Conversation
|
Thanks a lot for the PR. |
| @@ -0,0 +1,70 @@ | |||
| apiVersion: apps/v1 | |||
| kind: StatefulSet | |||
There was a problem hiding this comment.
Hi @melkypie
Great PR, thanks.
Just for my understanding, what are the benefits of a ss here vs dep?
There was a problem hiding this comment.
The leader of the gnmic cluster needs to be able to reach other cluster instances to assign them targets. If we used a deployment that is not possible. We can only reach other instances in a Deployment by using a Service which would randomly select a pod that is assigned to said service (this is also the reason why we need to use a headless Service ( service with clusterIP: none) for Prometheus service discovery as the DNS for a headless service will return all StatefulSet pod IPs rather than just one of them). With a StatefulSet each of the pods gets it's own specific DNS name, e.g. gnmic-ss-0.gnmic-svc.gnmic.svc.cluster.local, that allows the leader to contact each pod individually.
|
Thanks again for the PR @melkypie |
As promised in #560.
I had a question about the diagram, since it is in another branch, should I just make another pull request to that branch with the diagram added?