Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sig-node: Kubelet-in-UserNS, aka Rootless mode #2033

Open
AkihiroSuda opened this issue Sep 30, 2020 · 44 comments
Open

sig-node: Kubelet-in-UserNS, aka Rootless mode #2033

AkihiroSuda opened this issue Sep 30, 2020 · 44 comments
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status

Comments

@AkihiroSuda
Copy link
Member

AkihiroSuda commented Sep 30, 2020 •
edited
Loading

Enhancement Description
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 30, 2020
@AkihiroSuda AkihiroSuda mentioned this issue Sep 30, 2020
Merged
@AkihiroSuda
Copy link
Member Author

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 30, 2020
@kikisdeliveryservice kikisdeliveryservice added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Sep 30, 2020
@kikisdeliveryservice kikisdeliveryservice added this to the v1.20 milestone Sep 30, 2020
@kikisdeliveryservice kikisdeliveryservice added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 30, 2020
@kikisdeliveryservice
Copy link
Member

Thanks for opening this @AkihiroSuda !

As a reminder Enhancements Freeze is next Tuesday October 6th, by which time KEPs must be merged in an implementable state (you have this), have test plans(you have this) and graduation criteria (you have this).

@kendallroden
Copy link

kendallroden commented Oct 5, 2020 •
edited
Loading

Hi @AkihiroSuda , Just a reminder that the outstanding PR (#1371) must be merged by EOD PST tomorrow (10/6) for this KEP to be included in the Enhancements Freeze for the 1.20 release. After that time you will need to request an Exception to be included in the 1.20 Release.

Best,
Kendall
Enhancements Team 1.20

@kikisdeliveryservice
Copy link
Member

Hi @AkihiroSuda

Enhancements Freeze is now in effect. Unfortunately, your KEP PR did not merge. If you wish to be included in the 1.20 Release, please submit an Exception Request as soon as possible.

Best,
Kirsten
1.20 Enhancements Lead

@kikisdeliveryservice kikisdeliveryservice added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Oct 7, 2020
@kikisdeliveryservice kikisdeliveryservice removed this from the v1.20 milestone Oct 7, 2020
@alexandrevicenzi alexandrevicenzi mentioned this issue Dec 11, 2020
Open
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2021
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2021
This was referenced Feb 26, 2021
Closed
Closed
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 5, 2021
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 5, 2021
@george-angel
Copy link

/remove-lifecycle stale

@JamesLaverack JamesLaverack added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 5, 2021
@JamesLaverack JamesLaverack added this to the v1.22 milestone May 5, 2021
@gracenng
Copy link
Member

Hi @AkihiroSuda 👋 1.22 Enhancement shadow here.

This enhancement is well on its way, some minor change requests in light of Enhancement Freeze on Thursday May 13th:

  • Update kep.yaml file to the latest template, as well as fill in approvers prr-approvers and update milestones
  • Obtain a PRR approval

Thanks 😊

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 8, 2022
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 8, 2022
@rhockenbury
Copy link

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.22 milestone Oct 1, 2022
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2022
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 29, 2023
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 29, 2023
@AkihiroSuda AkihiroSuda mentioned this issue Feb 8, 2023
Merged
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2023
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2023
@Atharva-Shinde Atharva-Shinde added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 14, 2023
@AkihiroSuda AkihiroSuda mentioned this issue Sep 18, 2023
Closed
@AkihiroSuda
Copy link
Member Author

AkihiroSuda commented Sep 18, 2023 •
edited
Loading

As a baby step to set up the CI for this, I'm updating the KRTE image in test-infra to support Rootless Docker:

EDIT (Oct 17, 2023): the current plan is to spawn AWS or GCP VMs via kubetest2: kubernetes/test-infra#30744 (comment)

@AkihiroSuda
Copy link
Member Author

AkihiroSuda commented Oct 17, 2023 •
edited
Loading

Now all the [NodeConformance] tests pass with:

Not integrated to prow yet though

@AkihiroSuda
Copy link
Member Author

AkihiroSuda commented Oct 20, 2023 •
edited
Loading

PR for prow:

EDIT (Nov 30, 2023): failing due to:

@AkihiroSuda
Copy link
Member Author

Now CI is green:

@kannon92
Copy link
Contributor

With cgroup v2 promoted to GA, should we consider promoting this KEP to beta?

Esp with usernamespaces being promoted to beta in 1.30.

@AkihiroSuda
Copy link
Member Author

With cgroup v2 promoted to GA, should we consider promoting this KEP to beta?

Esp with usernamespaces being promoted to beta in 1.30.

Yes, let me try it in the v1.31 window

@AkihiroSuda
Copy link
Member Author

↑
I'm busy for another (unrelated) KEP #4668 , so I'll retry it in the v1.32 window

@kannon92
Copy link
Contributor

kannon92 commented Aug 20, 2024 •
edited
Loading

@AkihiroSuda will you be able to work on this for v1.32?

I'm going to mark this as proposed for consideration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
SIG Node 1.32 KEPs planning
Status: Triage
Milestone
No milestone
Development

No branches or pull requests