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

Client Exec Proxy #2718

Closed
1 of 4 tasks
nckturner opened this issue May 11, 2021 · 35 comments
Closed
1 of 4 tasks

Client Exec Proxy #2718

nckturner opened this issue May 11, 2021 · 35 comments
Assignees
@nckturner @mikedanese @enj @jeevanpuchakay
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status

Comments

@nckturner
Copy link
Contributor

nckturner commented May 11, 2021 •
edited by marosset
Loading

Enhancement Description

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

/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
@nckturner
Client Exec Proxy (kubernetes#2718)
1749701 
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@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 Aug 9, 2021
@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 Sep 8, 2021
@nckturner
Copy link
Contributor 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 Sep 8, 2021
nckturner added a commit to nckturner/enhancements that referenced this issue Sep 23, 2021
@nckturner
Client Exec Proxy (kubernetes#2718)
370ba70 
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@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 7, 2021
@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 6, 2022
nckturner added a commit to nckturner/enhancements that referenced this issue Jan 24, 2022
@nckturner
Client Exec Proxy (kubernetes#2718)
ed6487e 
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
@nckturner
Client Exec Proxy (kubernetes#2718)
cc1905a 
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
@nckturner
Client Exec Proxy (kubernetes#2718)
6e778ab 
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
@nckturner
Client Exec Proxy (kubernetes#2718)
37953a8 
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
@nckturner
Client Exec Proxy (kubernetes#2718)
542f82f 
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
@nckturner
Client Exec Proxy (kubernetes#2718)
fc8d2f5 
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
@nckturner
Client Exec Proxy (kubernetes#2718)
3ea7b9d 
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
@nckturner
Client Exec Proxy (kubernetes#2718)
1bc4b0c 
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@k8s-ci-robot k8s-ci-robot added this to the v1.27 milestone Nov 4, 2022
@rhockenbury
Copy link

/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
@enj enj added the lead-opted-in Denotes that an issue has been opted in to a release label Jan 10, 2023
@marosset
Copy link
Contributor

marosset commented Jan 31, 2023 •
edited
Loading

Hello @nckturner 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for v1.27 (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: v1.27
  • 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 latest-milestone and milestone.alpha in the kep.yaml to reflect a 1.27 alpha gradutaion

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!

ahmedtd pushed a commit to ahmedtd/enhancements that referenced this issue Feb 2, 2023
@nckturner @ahmedtd
Client Exec Proxy (kubernetes#2718)
d1599c1 
A KEP to propose a client-side proxy for a number of client
authentication use cases.
@marosset
Copy link
Contributor

marosset commented Feb 7, 2023

#3814

@marosset marosset 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 Feb 9, 2023
@marosset
Copy link
Contributor

marosset commented Mar 8, 2023

Hi @nckturner 👋,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

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.

Please let me know if there are any PRs in k/k I should be tracking for this KEP.

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

@enj
Copy link
Member

enj commented Mar 8, 2023

/milestone clear

We'll pick this back up next release.

@k8s-ci-robot k8s-ci-robot removed this from the v1.27 milestone Mar 8, 2023
@enj enj removed the lead-opted-in Denotes that an issue has been opted in to a release label Mar 8, 2023
@Atharva-Shinde Atharva-Shinde removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 14, 2023
@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 Jan 20, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue 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 Feb 19, 2024
@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 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:

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

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

/close not-planned

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 20, 2024
@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

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.

@jeevanpuchakay
Copy link

jeevanpuchakay commented Jun 1, 2024 •
edited
Loading

/assign
/reopen

@jeevanpuchakay
Copy link

/reopen

@k8s-ci-robot
Copy link
Contributor

@jeevanpuchakay: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

@jeevanpuchakay
Copy link

I would like to pick this up, can someone add me as a collaborator to this issue?

@enj enj mentioned this issue Jul 4, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nckturner nckturner

@mikedanese mikedanese

@enj enj

@jeevanpuchakay jeevanpuchakay

Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
(Test board) Kubernetes 1.26 Enhancements Tracking
Status: New New
1.26 Enhancements Tracking
Status: Net New
1.27 Enhancements Tracking
Status: Deferred
SIG Auth
Archived in project
Milestone
No milestone
Development

No branches or pull requests
10 participants
@nckturner @mikedanese @rhockenbury @enj @mickeyboxell @marosset @k8s-ci-robot @jeevanpuchakay @k8s-triage-robot @Atharva-Shinde