-
Notifications
You must be signed in to change notification settings - Fork 49
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
Exclude kubeconfig from airshipctl config use-context update #294
Comments
Related Change #741478Subject: Exclude kubeconfig from use-context update This change will close this issue when merged. ApprovalsCode-Review
+2 Dmitry Ukov
+2 Kostyantyn Kalynovskyi
Verified
+2 Zuul
Workflow
+1 Kostyantyn Kalynovskyi Last Updated: 2020-08-20 00:15:04 CDT |
Related Change #744382Subject: Adding kubeconfig interface ApprovalsCode-Review
! None
Verified
+1 Zuul
Workflow
! None Last Updated: 2020-08-07 11:30:04 CDT |
Related Change #745262Subject: Adding kubeconfig flags and provider ApprovalsCode-Review
-1 Dmitry Ukov
Verified
+1 Zuul
Workflow
! None Last Updated: 2020-08-13 21:15:03 CDT |
The Change that closes this issue was merged. |
Proposed change
When airshipctl config use-context is executed, the specified context should be switched in airshipconfig only. Per issue #264, kubeconfig has moved to the manifest document set and would be updated through kustomize and should not be included in the use-context update. This change should ensure kubeconfig is not part of use-context switching.
The text was updated successfully, but these errors were encountered: