Hi, Is there a configuration setting where, using the Kubernetes elastic agent plugin, the go server calls for an agent pod, however, the pods only get spun up on one worker node? This happens to the point where that worker node is 100% CPU and memory used, which makes the pipelines run to a crawl.
I have a 3 node Kubernetes cluster and there are 2 workers nodes sitting idle and the pipelines die due to one k8 worker node having all the pods running. I there something that I need to configure that allows the pods to be evenly distributed on the other 2 worker nodes? -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/2da6e638-ae35-4410-8f69-f626a6d20648n%40googlegroups.com.
