Score:0

HTTP(S) (Classic) Load Balancer keeps coming back after being deleted

be flag

I'm using a "Network (target pool-based) Load Balancer" for my application (with GKE on GCP).

I've tried playing around with creating a new "HTTP(S) (Classic) Load Balancer" which was never set up properly. I'm trying to delete it (as I'm being charged for it) because I don't need it, but after (successful) deletion, it usually takes 10minutes to an hour after which the same HTTP(s) load balancer returns.

I've double checked multiple times, there's nothing in my code or deploy pipeline which creates this. Would love to get help/documentation on how to permanently get rid of it.

Delete LoadBalancer Dialog

Deleted LoadBalancer

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.