KEP-4381: Add pciBusID standard device attribute definition

[varunrsekar]

• One-line PR description: This PR introduces one standard device attribute: resource.kubernetes.io/pciBusID. This attribute may be used to identify devices by their PCI bus address.

• Issue link: DRA: standardize parameter resource.kubernetes.io/pciAddress for the example pcie address of devices kubernetes#134569

• Other comments: None

/wg-device-management
/assign @johnbelamaric
/assign @klueska
/assign @pohly
/assign @mortent

[k8s-ci-robot]

Welcome @varunrsekar!

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 @varunrsekar. Thanks for your PR.

I'm waiting for a github.com 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.

[lmktfy]

We have a registry of well-known labels, annotations and taints.

Should we put a similar resource attribute registry on the website? Now there are two, it might be a good time to start that registry.

---

Want the registry to be YAML / KYAML / not-Markdown? That's fine, rendering pages based on machine readable data is a well understood thing for SIG Docs.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• keps/sig-node/OWNERS

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

[varunrsekar]

@lmktfy Agreed that we need to have a section in the website docs on this. I already have a PR in the work for that. I'm just waiting on reviews on this KEP PR to complete so that I can keep it aligned with the docs.