https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
c
why are you trying to delete them? They’re managed by klipper-lb so yes, if you delete them, it will re-create them as long as the service that requires them exists
v
@creamy-pencil-82913 when we stop the Load Balancer service, the svclb instances are not killed, as we have seen in the past. We restart the LB service (with new definitions), we seem to end up with conflicts of ports / names, due to the lingering svclbs
c
what do you mean by ‘stop’ the LB service. You mean the pods don’t get cleaned up when the service is deleted?
Kubernetes doesn’t really have a concept of “stopping” a Service. You can delete it, or delete (scale to 0) the pods that back it while leaving the service defined, but Services themselves don’t have a ‘started’ or ‘stopped’ state.
If you are deleting the service and the svclb pods remain, that’s a problem though.
v
Yes, we delete the LB service and the pods remain. We agree it is a bug. Is there a work around to get the pods to go away?
c
Would you mind opening a github issue?
Created https://github.com/k3s-io/k3s/issues/5823 for you, please add any additional details you can share
84 Views
Open in Slack
PreviousNext
Powered by