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.

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

Client Exec Proxy #2718

Open
4 tasks
nckturner opened this issue May 11, 2021 · 23 comments
Open
4 tasks

Client Exec Proxy #2718

nckturner opened this issue May 11, 2021 · 23 comments
Assignees
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. 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
Projects
Milestone

Comments

@nckturner
Copy link
Contributor

nckturner commented May 11, 2021

Enhancement Description

  • One-line enhancement description (can be used as a release note): A client-side proxy for a number of client authentication use cases.
  • Kubernetes Enhancement Proposal: Client Exec Proxy #2693
  • Discussion Link: SIG-Auth discussion on 2021-04-28
  • Primary contact (assignee): @nckturner
  • Responsible SIGs: SIG-Auth
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y): 1.26
    • Beta release target (x.y): 1.27
    • Stable release target (x.y): 1.28
  • Alpha
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 11, 2021
@nckturner
Copy link
Contributor Author

nckturner commented May 11, 2021

/sig auth

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 11, 2021
nckturner added a commit to nckturner/enhancements that referenced this issue May 11, 2021
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@enj enj added this to Needs Triage Issues in SIG Auth May 17, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 9, 2021

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 Aug 9, 2021
@enj enj moved this from Needs Triage to In Review in SIG Auth Aug 16, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 8, 2021

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 Sep 8, 2021
@nckturner
Copy link
Contributor Author

nckturner commented Sep 8, 2021

/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 Sep 8, 2021
nckturner added a commit to nckturner/enhancements that referenced this issue Sep 23, 2021
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@k8s-triage-robot
Copy link

k8s-triage-robot commented Dec 7, 2021

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 7, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Jan 6, 2022

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 6, 2022
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 24, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 24, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 24, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@enj
Copy link
Member

enj commented Jan 27, 2022

/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 27, 2022
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 28, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 28, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 28, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 28, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 28, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
SIG Auth automation moved this from Closed / Done to Needs Triage Jun 27, 2022
@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 Jun 27, 2022
@enj enj added lead-opted-in Denotes that an issue has been opted in to a release stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Sep 9, 2022
@enj enj added this to the v1.26 milestone Sep 9, 2022
@rhockenbury rhockenbury added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 18, 2022
@rhockenbury
Copy link

rhockenbury commented Sep 18, 2022

Hello @nckturner 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.26
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:

  • Update the PRR approver file to include stage alpha
  • Update the test plan section to reflect changes in the KEP template filled out
  • Update latest-milestone and milestone in the KEP file
  • After updating, please plan to merge Client Exec Proxy #2693 before enhancements freeze

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

nckturner added a commit to nckturner/enhancements that referenced this issue Sep 29, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@rhockenbury
Copy link

rhockenbury commented Oct 1, 2022

Quick reminder - Enhancement freeze is about a week away. If you are still looking to get this enhancement into v1.26, please plan to get #2693 merged before enhancement freeze.

@enj enj moved this from Needs Triage to In Progress in SIG Auth Oct 3, 2022
nckturner added a commit to nckturner/enhancements that referenced this issue Oct 6, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
nckturner added a commit to nckturner/enhancements that referenced this issue Oct 6, 2022
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@enj
Copy link
Member

enj commented Oct 7, 2022

@rhockenbury #2693 has been approved by SIG Auth leads and PRR #2693 (comment) - we are just waiting on explicit /approve from PRR folks.

@enj
Copy link
Member

enj commented Oct 7, 2022

@rhockenbury and now #2693 is merged 😄

@rhockenbury
Copy link

rhockenbury commented Oct 7, 2022

Hey @enj, It looks like the KEP readme needs a few updates to comply with the latest test plan template, specifically around the Test Plan section. I'm going to mark this as tracked but can you please get these changes in ASAP.

@mickeyboxell
Copy link

mickeyboxell commented Oct 20, 2022

@nckturner Are docs required for this KEP? If so, who will be opening the docs PR for k/website?

@marosset
Copy link
Contributor

marosset commented Oct 31, 2022

Hi @nckturner 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

For this enhancement, I do not see any k/k PRs linked to this issue.
Please plan to get PRs out for all k/k code so it can be merged up by code freeze.
If you do have k/k PRs open, please link them in the initial issue description.

As always, we are here to help should questions come up. Thanks!

@mickeyboxell
Copy link

mickeyboxell commented Nov 2, 2022

Hi @nckturner 👋 1.26 Release Docs shadow here. This enhancement is marked as Needs Docs for 1.26 release. Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time. It must be created by November 9. For more information, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

@enj enj removed the lead-opted-in Denotes that an issue has been opted in to a release label Nov 4, 2022
@enj
Copy link
Member

enj commented Nov 4, 2022

/milestone v1.27

Pushing this out to next release as we are out of time in v1.26.

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.26, v1.27 Nov 4, 2022
@enj enj moved this from In Progress to Backlog in SIG Auth Nov 4, 2022
@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

/label tracked/no
/remove-label tracked/yes

@k8s-ci-robot k8s-ci-robot 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 Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. 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
Projects
Status: Net New
SIG Auth
Backlog
Development

No branches or pull requests

8 participants