Transformation of Blueprints into k0rdent templates. #347
Conversation
|
|
||
| # k0rdent templates | ||
|
|
||
| k0rdent templates are re-usable text definitions of components that you can use |
There was a problem hiding this comment.
This is a chicken and egg problem and it's currently backwards.
There isn't a k0rdent template for creating an MKE4 cluster. Not at the moment. That's a future issue.
The flow is that MKE creates k0rdent templates and that are used to create a k0rdent cluster. This reads as the other way around.
| weight: 3 | ||
| --- | ||
|
|
||
| # k0rdent templates |
There was a problem hiding this comment.
Something in here should mention that MKE is creating and managing these k0rdent templates. The current description would make me think I can edit these as a user. We don't expose these in an easy to edit way. Someone can go change them in the cluster, but the mke-operator will reconcile and wipe out their changes. Wording here can set better expectations for the user.
There was a problem hiding this comment.
I think wording here should be along the lines of
We chose to build on top of k0rdent templates because...
| can configure a template so that non-admin users can only execute templates | ||
| that deploy a particular set of controllers. | ||
|
|
||
| ## Template types ## |
There was a problem hiding this comment.
We should reference the k0rdent docs for each template type for those that are wanting to read about them in more detail. Keep everything here high level.
No description provided.