dynamic resource allocation: "extending Kubernetes" documentation

[pohly]

What would you like to be added?

https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/ describes CSI, device plugins and other extension points.

It would be useful to have a page there about DRA.

Why is this needed?

It would help vendors who want to create their own DRA driver.

[k8s-ci-robot]

@pohly: 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.

[pohly]

/sig node

[sftim]

I recommend moving this to k/website

/transfer website

[sftim]

/language en

[divya-mohan0209]

/triage accepted

[yrs147]

I would like to work on this issue

[yrs147]

/assign @yrs147

[yrs147]

I'm having an issue setting up the website on my local

@divya-mohan0209 @sftim, can you please tell me how to fix this, cause I've tried everything.

[pohly]

@kannon92: perhaps this is something that you could pick up?

[kannon92]

Sure.
/assign

[kannon92]

@pohly One thing I worry about is that since DRA is alpha I wonder if we should just link https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/ rather than creating a new page like we did for device-plugins/ CNI plugins.

[pohly]

The existing page is more oriented towards users. What we want is something for developers.

[kannon92]

I am afraid I won't be able to work on this issue. I thought I'd be working on more DRA items but things did not turn out that way.

/unassign

[byako]

/assign

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[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

[pohly]

/remove-lifecycle stale

[pohly]

/wg device-management