-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stale NBs are left when deleting the underlying K8S cluster #140
Comments
any thoughts on what we could catch to make this happen? this is happening outside of kube so we can't use the lifecycles in the ccm... my only thought is if the vms are deleted via the linode api we'd have do some reconcile with nodebalancers e.g. if their underlying nodes dont exist any more we delete the nodebalancer. open to suggestions @schinmai-akamai any other ideas ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
General:
Bug Reporting
When using the Linode CCM in K8S clusters and deleting the underlying cluster while not deleting the
Service
leaves a stable NB in the Linode account.Expected Behavior
Explore having some kind of finalization mechanism to delete the NB when the cluster is being deleted
Actual Behavior
Stale NBs are left in place
Steps to Reproduce the Problem
Environment Specifications
This happens for KPP clusters but also was reported by externally facing customers who are not using KPP
Additional Notes
I'm not really sure we can address this in the linode-ccm and may need to address it at a platform level but wanted to have this logged and tracked somewhere
For general help or discussion, join the Kubernetes Slack team channel
#linode
. To sign up, use the Kubernetes Slack inviter.The Linode Community is a great place to get additional support.
The text was updated successfully, but these errors were encountered: