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

Extracting/Migrating the Credential Provider: KEP + Alpha Implementation #13

Open
andrewsykim opened this issue Feb 21, 2019 · 14 comments
Open

Extracting/Migrating the Credential Provider: KEP + Alpha Implementation #13

andrewsykim opened this issue Feb 21, 2019 · 14 comments
Assignees
@mcrute @nckturner @M00nF1sh
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. P0 Priority 0
Milestone
v1.19

Comments

@andrewsykim
Copy link
Member

As part of the cloud provider extraction/migration, we should start to look into how the credential provider is going to be extracted so that the kubelet does not rely on cloud SDKs for image pulling credentials. Also to support future credential providers without adding it into the main tree.

Need to work with SIG Auth and propose a KEP to extract/migrate credential providers to move out-of-tree.

related: kubernetes/kubernetes#68810

cc @justinsb @mcrute
@andrewsykim andrewsykim added this to the Next milestone Feb 21, 2019
@andrewsykim andrewsykim mentioned this issue Feb 22, 2019
Closed
@mcrute
Copy link
Contributor

mcrute commented Feb 23, 2019

/assign @mcrute

@mcrute
Copy link
Contributor

mcrute commented Feb 23, 2019

Also related kubernetes/kubernetes#70675

@andrewsykim
Copy link
Member Author

@mcrute and I are doodling out some ideas for this, hoping we can have an alpha feature-gated version of this in for v1.15.

cc @liggitt @smarterclayton

@andrewsykim andrewsykim modified the milestones: Next, v1.15 Mar 6, 2019
@feiskyer
Copy link
Member

Would secret a possible solution for this?

This was referenced Mar 20, 2019
Closed
Closed
@andrewsykim
Copy link
Member Author

Would secret a possible solution for this?

Yes, this is one of the possible solutions we're discussing. KEP is work in progress :)

@andrewsykim
Copy link
Member Author

andrewsykim commented Mar 20, 2019 •
edited
Loading

/milestone v1.15
/priority critical-urgent

cc @dchen1107 @derekwaynecarr

@k8s-ci-robot k8s-ci-robot added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Mar 20, 2019
@andrewsykim andrewsykim modified the milestones: Next, v1.15 Mar 20, 2019
@andrewsykim andrewsykim added P0 Priority 0 and removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Mar 28, 2019
@andrewsykim
Copy link
Member Author

andrewsykim commented Mar 28, 2019 •
edited
Loading

For v1.15, p0: KEP + alpha implementation

@k8s-ci-robot k8s-ci-robot added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Mar 28, 2019
@andrewsykim andrewsykim removed the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Mar 28, 2019
@mcrute
Copy link
Contributor

mcrute commented Apr 11, 2019

Rough draft of the KEP, mostly just the problem statement at this point.

@feiskyer
Copy link
Member

For v1.15, p0: KEP + alpha implementation

@andrewsykim What's your proposal for alpha implementation?

@andrewsykim andrewsykim changed the title Extracting/Migrating the Credential Provider Extracting/Migrating the Credential Provider: KEP + Alpha Implementation Apr 13, 2019
@andrewsykim andrewsykim modified the milestones: v1.15, v1.16 Jun 12, 2019
@andrewsykim andrewsykim mentioned this issue Aug 15, 2019
Merged
@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 Sep 10, 2019
@andrewsykim
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 Sep 11, 2019
@andrewsykim andrewsykim assigned mcrute, nckturner and M00nF1sh and unassigned mcrute Oct 2, 2019
@andrewsykim andrewsykim modified the milestones: v1.16, v1.17 Oct 2, 2019
@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 Dec 31, 2019
@cheftako
Copy link
Member

cheftako commented Jan 2, 2020

/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 2, 2020
@cheftako
Copy link
Member

cheftako commented Jan 2, 2020

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 2, 2020
@andrewsykim andrewsykim modified the milestones: v1.17, v1.18 Jan 22, 2020
@invidian invidian mentioned this issue Feb 11, 2020
Closed
@andrewsykim andrewsykim modified the milestones: v1.18, v1.19 Apr 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mcrute mcrute

@nckturner nckturner

@M00nF1sh M00nF1sh

Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. P0 Priority 0
Projects
None yet
Milestone
v1.19
Development

No branches or pull requests
8 participants
@mcrute @feiskyer @cheftako @nckturner @andrewsykim @k8s-ci-robot @fejta-bot @M00nF1sh