KEP 4680: Update README.md for DRA

[Jpsassine]

This update transfers the design details from https://docs.google.com/document/d/1CopUHEeTebGeSb3jvmHkpABACAnrDFj5OCmEqRSKCDY/edit?usp=sharing

• One-line PR description: Updating the KEP to include the detailed design for updating pod status with device health for DRA.

• Issue link: Add Resource Health Status to the Pod Status for Device Plugin and DRA #4680

• Reference doc https://docs.google.com/document/d/1CopUHEeTebGeSb3jvmHkpABACAnrDFj5OCmEqRSKCDY/edit?usp=sharing

• Other comments:

[k8s-ci-robot]

Welcome @Jpsassine!

It looks like this is your first PR to kubernetes/enhancements 🎉. 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/enhancements 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. 😃

[k8s-ci-robot]

Hi @Jpsassine. 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.

Details

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.

[Jpsassine]

cc/ @SergeyKanzhelev @ArangoGutierrez

[SergeyKanzhelev]

/ok-to-test

[SergeyKanzhelev]

cc: @pohly @bart0sh @johnbelamaric

[bart0sh]

/cc @klueska

[mortent]

/wg device-management

[SergeyKanzhelev]

/assign @pohly

@pohly any concerns with this design?

[pohly]

No major concerns from me about the design. It's quite a bit of additional code and complexity and feels a bit redundant, but I understand that surfacing the health information in the pod status needs it.

Some nit and suggestions.

[pohly]

xref: #5104 (comment)

TLDR: "device name" will become <device name>[/<share ID>] once consumable capacities allow allocating the same device multiple times. This is consistent with the proposed API here, it just needs an updated description - but not now! It depends on the order in which the implementations get merged.

cc @sunya-ch

[mrunalp]

Looks good. Thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jpsassine, mrunalp

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• keps/sig-node/OWNERS [mrunalp]

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

[mrunalp]

/lgtm