To elaborate on the previous post, I did some further investigations on using the deployment object and found that the behaviour described above will happen when adding liveness and readiness probes to the YAML file. Is it recommended to add the probes to the deployment YAML file? Thanks.
On Fri, Dec 23, 2022 at 9:57 AM Wen Bo (Bill) Li <[email protected]> wrote: > Forgot to attach the link for the documentation: > https://ignite.apache.org/docs/latest/installation/kubernetes/gke-deployment > > On Fri, Dec 23, 2022 at 1:43 AM Wen Bo (Bill) Li <[email protected]> > wrote: > >> Hi, >> >> I have encountered an issue in deploying Ignite on Kubernetes using the >> deployment object. By following the documentation below, I deployed an >> Ignite cluster with 3 instances. However, because these 3 instances started >> all at the same time, they did not discover each other at the startup and >> became 3 standalone clusters. It will try to discover an existing cluster >> and become part of it only when I restart any of the pods. Has anyone >> encountered this issue before? >> >> Regards, >> >> -- >> >> Wen Bo (Bill) Li (he, him, his) >> Geotab >> >> Senior Software Developer, Data Platform >> >> Direct >> Toll-free >> >> Visit >> >> +1 (416) 908-2988 >> +1 (877) 431-8221 >> www.geotab.com >> >> Twitter <https://twitter.com/geotab> | Facebook >> <https://www.facebook.com/Geotab> | YouTube >> <https://www.youtube.com/user/MyGeotab> | LinkedIn >> <https://www.linkedin.com/company/geotab/> >> >
