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

[0.1] Pivot kubeconfig secrets #1316

Closed
ncdc opened this issue Aug 23, 2019 · 4 comments
Closed

[0.1] Pivot kubeconfig secrets #1316

ncdc opened this issue Aug 23, 2019 · 4 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@ncdc
Copy link
Contributor

ncdc commented Aug 23, 2019

/kind feature

Describe the solution you'd like
Currently if any KubeConfig secrets are created pre-pivot, these secrets must be recreated post-pivot since the secrets are not moved as part of the pivot. I'd like to see the secrets moved as part of the pivot in order to simplify the post-pivot edge cases.

@ncdc ncdc added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 23, 2019
@ncdc ncdc added this to the v0.1.x milestone Aug 23, 2019
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 23, 2019
@tahsinrahman
Copy link
Contributor

/assign
/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Aug 31, 2019
@tahsinrahman
Copy link
Contributor

Don't we need the same for other releases?

@detiber
Copy link
Member

detiber commented Sep 5, 2019

This should already be the case for v0.2.x
/close

@k8s-ci-robot
Copy link
Contributor

@detiber: Closing this issue.

In response to this:

This should already be the case for v0.2.x
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

4 participants