Replies: 4 comments
-
@mjudeikis these are awesome questions - I love the specificity and how clearly you've laid them out. We're likely to respond in this thread but while we work on our documentation story we will also make sure that all of these concepts are covered there, and if you're up to it, we might tag you for review on those to make sure the docs make sense! |
Beta Was this translation helpful? Give feedback.
-
Have you read https://github.com/kcp-dev/kcp/blob/main/docs/workspaces.md and/or https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md (we ideally should dedupe...)? Do those answer any of your questions?
"Virtual workspace" is:
We'll work on improving the docs around them (and hopefully finding a better name)
WIP docs on APIs in kcp: https://hackmd.io/DJGw8YdQTaiPKz9a66Z6OQ |
Beta Was this translation helpful? Give feedback.
-
| Have you read https://github.com/kcp-dev/kcp/blob/main/docs/workspaces.md and/or https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md (we ideally should dedupe...)? Do those answer any of your questions? I did read it but I found it very much specific to KCP and some analogies would be great. Like you can understand expected hiararchy of the workspaces from this document, but how does workspace maps into physical/wirtual clusters - its not clear. Like if I Create And ontop |
Beta Was this translation helpful? Give feedback.
-
Bonus things to consider adding:
|
Beta Was this translation helpful? Give feedback.
-
And after trying to use KCP I got a feeling of terminology overload and how to access certain objects (like
SyncTargets
iskubectl get synctargets
andworkspaces
has its ownkubectl
extension 🤯 ). So not only confusing how to interact with diffent objects but why they are named in one or another way.I dont think there is need to change any of them but some clarity would be good on terminology and background:
Workspaces
and workspace types: Does the 1 workspace maps to 1 cluster (I think no, but would be good to be explisit)? Which Workspace types should be given to end-users? Is the Workspace something like "Fake/Virtual cluster" or is it someting else? Why do I need workspaces in the first place?How does
VirtualWorkspace
plays into all this?SyncTarget
(In the docs stillWorkspaceCluster
) - How does these relate to physcial clusters and where is the boundary. Is the good practice to create all theSyncTargets
into root workspace or some other workspaces?APIBindings
- its not clear yet how users should use those from the docs.Workspace CLI
- I like the idea of workspace cli beingcd
,~
behaviour. But it feel very much out of context in kubectl pattern. Especially if I can't dols
rm
, etc. It looks bit half baked. Is there reason for differnet behaviour outside standart patternget, list, delete, etc
in this context?Overall I understand community is trying to avoid term overload (Cluster, VirtualCluster, EphemeralCluster, FakeCluster) and new terminolgy is potentially is being used (SyncTargets, Workloads, Workspaces, VirtualWorkspaces).
Would be nice to have some kind of pseudo mappping for terminology to hel users to mentaly translate terminoogy they know to KCP terminology, and maybe some good practices how it should be structured.
I think I will have more once I dig deeper into
Beta Was this translation helpful? Give feedback.
All reactions