Please note that we're already in Test Freeze for the release-1.34 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.34.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Thu Aug 7 03:00:08 UTC 2025.

The committers listed above are authorized under a signed CLA.

• ✅ login: ravisastryk / name: Ravi Sastry Kadali (58d6d89)

Welcome @ravisastryk!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Hi @ravisastryk. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ravisastryk
Once this PR has been reviewed and has the lgtm label, please assign dom4ha for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

/assign @ravisastryk

Aren't these two functions equivalent?

// Delete removes all items from the set.
func (s Set[T]) Delete(items ...T) Set[T] {
	for _, item := range items {
		delete(s, item)
	}
	return s
}

Seems set.Delete simply calls delete, it's just this function can handle multiple keys.

Aren't these two functions equivalent?

// Delete removes all items from the set.
func (s Set[T]) Delete(items ...T) Set[T] {
	for _, item := range items {
		delete(s, item)
	}
	return s
}

Seems set.Delete simply calls delete, it's just this function can handle multiple keys.

Thank you for your quick review @AxeZhan. You are right sets.Set[T], is just map[T]Empty under the hood. Both are functionally identical and apparently both deletion methods are same and the potential problem is not in this path.

I attempted couple of approaches in the cache management but does seem to be the root cause.

However, I discovered now that memory leak is potentially happening in the Kubernetes framework, in particular pods removal code path. It was caused by improper slice element removal in the removeFromSlice()
When pods were removed from NodeInfo slices (Pods, PodsWithAffinity, PodsWithRequiredAntiAffinity), the function was:

1. Moving the last element to the deleted position
2. Shrinking slice s = s[:len(s) - 1]
3. But not clearing the moved element reference. This is the fix I am proposing to explicitly clear the reference.

/ok-to-test

/retest

/retest-required

@ravisastryk: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.