feat :Add GetActivePods to handle/datastore and remove deleted pod from prefix-cache scorer

[kfirtoledo]

This PR introduces two main enhancements:

1. GetActivePods support in the plugin handle and datastore

• Added GetActivePods() method to plugins.Handle interface.
• Updated eppHandle to store and call a GetActivePodsFunc.
• Implemented GetActivePods in the datastore to return the list of currently active pods.

2. Remove deleted pod from prefix-cache scorer

• Added RemovePod method to prefix.indexer to remove a pod
• This enables cleanup of deleted pod after period of time that pod becomes inactive.

These changes allow plugins to query active pods directly from the handle and support cache cleanup for inactive pods in the prefix-cache scorer (Fix #1289)

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	138883a
🔍 Latest deploy log	https://app.netlify.com/projects/gateway-api-inference-extension/deploys/68e8ff7e453b17000839e1b5
😎 Deploy Preview	https://deploy-preview-1376--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

Hi @kfirtoledo. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kfirtoledo]

/assign @nirrozenbaum

[kfirtoledo]

/hold

[ahg-g]

@elevran is this aligned with the new datalayer APIs?

[elevran]

@elevran is this aligned with the new datalayer APIs?

I don't see a conflict - the datastore API is minimally affected.
Might be cleaner to allow registration for cleanup or Pod deletion instead of listing all Pods periodically, but this is not something I've touched in the data layer yet (plan to refactor the k8s data sources as well, as we discussed on the original design issue).

[liu-cong]

/lgtm

[liu-cong]

/ok-to-test

[liu-cong]

/lgtm

[kfswain]

Hey @kfirtoledo I see you have a hold on this PR, is this something we are still working on?

[kfirtoledo]

Hi, @kfswain I wasn't able to check it in e2e test, I was waiting the quickstart will work after all the v.1.0 changes

[danehans]

@kfirtoledo now that v1.0.0 (and subsequently v1.0.1) was cut, can you follow-up on #1376 (comment), resolve the merge conflict, etc?

[kfswain]

Heya @kfirtoledo just an FYI, we plan on cutting an RC for the next release sometime next week, if we wanted to include this it should try to merge before then.

[kfirtoledo]

/unhold

[kfirtoledo]

@liu-cong, @kfswain @danehans - I was able to test it on the new version v1.0.1 (now the getting started works)- so from my side it is fine now to merge

[liu-cong]

/lgtm

I am OK with merging this without a complete benchmark, as it introduces an async cleanup and doesn't change the main prefix score code path. Our automatic regression test should be able to capture it should any regression is introduced.

[kfswain]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kfirtoledo, kfswain

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kfswain]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment