Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Stale NBs are left when deleting the underlying K8S cluster

Open
  • Is something wrong?
#140 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, kubernetes
Domain
cloud, infrastructure

Research direction

Start by reproducing the issue with a Linode CCM Kubernetes cluster, a Service of type LoadBalancer, and deletion of the control plane and nodes while retaining the Service. Trace whether cleanup belongs in the Linode CCM or at the platform level, and determine the appropriate finalization point. Done means the underlying NodeBalancer is removed when the cluster is deleted, or the ownership boundary is documented if the CCM cannot address it.

Written by the indexing model from the issue text.

Description

General:

  • Have you removed all sensitive information, including but not limited to access keys and passwords?
  • Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?

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
  1. Create a K8S cluster with the linode-ccm installed on it
  2. Provision a Service of type LoadBalancer
  3. Delete the control plane and nodes of the cluster
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.

Dominant language
Go
Stars
94
Forks
75
Avg merge
1d 20h
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linode/linode-cloud-controller-manager

All issues in linode/linode-cloud-controller-manager

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.