enhancements icon indicating copy to clipboard operation
enhancements copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

KEP-2857: Runtime Assisted Mounting of Persistent Volumes

Open ddebroy opened this issue 4 years ago • 13 comments

  • One-line PR description: Provisional KEP for Runtime Assisted Mounting of Persistent Volumes
  • Issue link: https://github.com/kubernetes/enhancements/issues/2857
  • Other comments: Initial KEP PR

ddebroy avatar Aug 24 '21 00:08 ddebroy

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Dec 05 '21 15:12 k8s-triage-robot

/remove-lifecycle stale

ddebroy avatar Dec 07 '21 00:12 ddebroy

We (Databricks) have a use case that are blocked this KEP. Without this, it's really awkward to use block devices with VM based containers.

fengwang666 avatar Dec 07 '21 02:12 fengwang666

Update from sig-node on Feb 8th: the CRUST APIs between Kubelet <=> Runtime Handler will have to be plumbed through CRI APIs. Runtime handler specific actions in Kubelet is not desired.

ddebroy avatar Feb 08 '22 22:02 ddebroy

@ddebroy This is very interesting. I added an issue on the Kata side to make sure we track this.

Are you aware of any similar effort for CNI? I'm asking because Kata has very similar requirements / needs there.

c3d avatar Feb 09 '22 11:02 c3d

@c3d thanks! I am not aware of a similar effort for CNI. I could be wrong but my understanding is that with containerd/crio, most of the CNI interactions are handled by the CRI runtime. So that could be accomplished without Kubelet changes?

ddebroy avatar Feb 09 '22 16:02 ddebroy

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar May 10 '22 17:05 k8s-triage-robot

/remove-lifecycle stale

ddebroy avatar May 10 '22 21:05 ddebroy

Restructured the KEP to align with existing infra in Kata around runtime assisted mounts and avoid changes to CRI/OCI as well as RuntimeClass.

ddebroy avatar May 24 '22 11:05 ddebroy

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Sep 01 '22 21:09 k8s-triage-robot

/remove-lifecycle stale

ddebroy avatar Sep 01 '22 22:09 ddebroy

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ddebroy Once this PR has been reviewed and has the lgtm label, please assign johnbelamaric, jsafrane for approval by writing /assign @johnbelamaric @jsafrane in a comment. For more information see:The Kubernetes 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:

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

k8s-ci-robot avatar Sep 29 '22 10:09 k8s-ci-robot

/sig node

xing-yang avatar Oct 05 '22 17:10 xing-yang

/cc @zvonkok

zvonkok avatar Dec 14 '22 11:12 zvonkok

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

k8s-triage-robot avatar Mar 14 '23 12:03 k8s-triage-robot

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle rotten

k8s-triage-robot avatar Apr 13 '23 12:04 k8s-triage-robot

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

This bot triages PRs 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 PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

k8s-triage-robot avatar May 13 '23 12:05 k8s-triage-robot

@k8s-triage-robot: Closed this PR.

In response to this:

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

This bot triages PRs 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 PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

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.

k8s-ci-robot avatar May 13 '23 12:05 k8s-ci-robot

@ddebroy Are you still working on this?

haosdent avatar Jan 29 '24 10:01 haosdent

hi, I am not at this point - we ran into some significant challenges with a PoC of this at scale.

ddebroy avatar Jan 29 '24 21:01 ddebroy