It can be seen above that the es-master pod named es-master-594b58b86c-bj7g7 was elected as the leader and the other 2 pods were added to the cluster. root$ kubectl -n elasticsearch logs -f po/es-master-594b58b86c-9jkj2 | grep ClusterApplierService When following the logs of the master-nodes, you will also see when new data and client nodes are added. This is when the master-node pods choose which one is the leader of the group. If you follow the logs of any of the master-node pods, you will witness the master election among them. Image: quay.io/pires/docker-elasticsearch-kubernetes:6.2.4 PreferredDuringSchedulingIgnoredDuringExecution: Deployment and Headless Service for Master Nodesĭeploy the following manifest to create master nodes and the headless service: Let’s jump right at deploying these services to our GKE cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |