Score:0

Google Load Balancer refuses to save backend ports for GKE after node pool migration

us flag
Ral

I recently migrated my working deployment from a small node group to a large one using this guide. Everything seems to be working fine, however the Google load balancer which is set up in front of my GKE cluster cannot seem to be fully updated to point to the new instance group.

I have configured all backends to the new node pool perfectly fine, however 2 out of the 3 backends have lost the correct port. I go to edit the load balancer and put the new ports, but whenever I apply the changes, the load balancer configuration does not update. 2 of the 3 backends do not seem to be able to have a port assigned to them. The backend type is "instance groups"

Score:0
us flag
Ral

I have just fixed this problem by using the 'backends' tab, clicking the backend I want to add the port to, then setting it and saving it there in what I assume is the legacy page for configuring backends.

I believe this is an issue with the all-in-one 'edit load balancer' page found by clicking the pencil "edit" button at the top of the page while viewing a load balancer.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.