Dynamic resource allocation: refactoring overall flow of prepare/unprepare resources

[TommyStarK]

• Implement a clean way to determine which API the gRPC server supports
  Proposal:
  - detect version in a lazy way, i.e. on the first real call and only set the version if the call succeeds
  - better approach could be to specify supported API version at the plugin registration time but it implies deeper changes as it affects devices plugins and csi plugins
• Avoid falling back to v1alpha2 API on every call
• Update end-to-end tests using KIND
• Update dra e2e node tests

Tasks

Beta Give feedback

No tasks being tracked yet.

[k8s-ci-robot]

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.

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/test-infra repository.

[TommyStarK]

/sig node
/area kubelet
/assign
/cc @bart0sh @klueska

[bart0sh]

Update end-to-end tests using KIND

Do you mean fix failing tests or add new ones?

[TommyStarK]

I mean both, imo we will need to update the current tests but also add new ones to test our changes are working as expected

[bart0sh]

Thanks for the explanations. btw, dra e2e node tests doesn't use kind. are you planning to update them?

[TommyStarK]

I forgot about the dra e2e node tests. IMHO we should also look at them. I've updated the issue accordingly. I know this is going to be a big amount of work but I do think it's necessary.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[bart0sh]

/close
The issue is fixed by #120099

[k8s-ci-robot]

@bart0sh: Closing this issue.

In response to this:

/close
The issue is fixed by #120099

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/test-infra repository.