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

5. kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics #778

Merged
merged 6 commits into from
Mar 31, 2022

Conversation

sttts
Copy link
Member

@sttts sttts commented Mar 25, 2022

Implementing UX from https://docs.google.com/document/d/1XJJCr16bg22QuJnQB2W98A-djRTtrLr2JE2IWZUHzJU/edit#heading=h.nn8danthd1ys.

Based on #744.

@sttts sttts requested a review from davidfestal March 25, 2022 21:17
@sttts sttts added the area/logical-cluster Related to logical clusters label Mar 25, 2022
@sttts sttts added this to the Prototype 4 milestone Mar 25, 2022
@sttts sttts added kind/feature Categorizes issue or PR as related to a new feature. severity/experience-blocker Something that considerably blocks the user experience of kcp labels Mar 25, 2022
@sttts sttts force-pushed the sttts-kcp-logicalcluster-kubectl-kcp branch from c54cc88 to 398fa63 Compare March 25, 2022 21:41
@sttts sttts changed the title kubectl-kcp: implement workspace hierarchy kubectl-kcp: implement workspace hierarchy and get rid of workspace duality Mar 25, 2022
@sttts sttts changed the title kubectl-kcp: implement workspace hierarchy and get rid of workspace duality kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics Mar 25, 2022
@sttts sttts changed the title kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics 3. kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics Mar 26, 2022
@sttts sttts changed the title 3. kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics 4. kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics Mar 26, 2022
@sttts sttts force-pushed the sttts-kcp-logicalcluster-kubectl-kcp branch 2 times, most recently from 9851181 to a705aa9 Compare March 27, 2022 11:10
@sttts sttts changed the title 4. kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics 5. kubectl-kcp: get rid of workspace duality and implement logical cluster path semantics Mar 27, 2022
@sttts sttts force-pushed the sttts-kcp-logicalcluster-kubectl-kcp branch 3 times, most recently from 4ae5008 to f8d398e Compare March 28, 2022 11:55
@sttts sttts mentioned this pull request Mar 28, 2022
@sttts sttts force-pushed the sttts-kcp-logicalcluster-kubectl-kcp branch 4 times, most recently from 60ec028 to c872c4a Compare March 29, 2022 13:56
@sttts sttts force-pushed the sttts-kcp-logicalcluster-kubectl-kcp branch from c872c4a to 75ae0a6 Compare March 29, 2022 18:05
pkg/cliplugins/workspace/cmd/cmd.go Show resolved Hide resolved
pkg/cliplugins/workspace/plugin/helpers.go Show resolved Hide resolved
pkg/server/handler.go Outdated Show resolved Hide resolved
pkg/server/handler.go Outdated Show resolved Hide resolved
pkg/cliplugins/workspace/plugin/kubeconfig.go Outdated Show resolved Hide resolved
pkg/cliplugins/workspace/plugin/kubeconfig.go Outdated Show resolved Hide resolved
}
newCluster := *oldCluster
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So you don't manage AuthInfo at all in the current and previous context ?
Afair in previous tests I had done, it might bring some very painful behavior where you cannot bring back the auth used (through a --token override for example) with the previous workspace.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I think this needs to be carried forward

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on @sttts 's comment in Slack

verified that overrides don't affect what is persisted. This is what kubectl itself does too. overrides are only used to tweak a client used by kubectl/the plugin.

👍

pkg/cliplugins/workspace/plugin/kubeconfig.go Show resolved Hide resolved
@sttts sttts force-pushed the sttts-kcp-logicalcluster-kubectl-kcp branch from 9ccabd8 to ace68a1 Compare March 31, 2022 13:28
pkg/cliplugins/workspace/cmd/cmd.go Outdated Show resolved Hide resolved
pkg/cliplugins/workspace/cmd/cmd.go Outdated Show resolved Hide resolved
}
newCluster := *oldCluster
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on @sttts 's comment in Slack

verified that overrides don't affect what is persisted. This is what kubectl itself does too. overrides are only used to tweak a client used by kubectl/the plugin.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logical-cluster Related to logical clusters kind/feature Categorizes issue or PR as related to a new feature. severity/experience-blocker Something that considerably blocks the user experience of kcp
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants