namespace provisioning using UI
#3113
Conversation
| @@ -1,4 +1,4 @@ | |||
| # Namespace provisioning example via kpt CLI | |||
| # Namespace provisioning using kpt CLI | |||
There was a problem hiding this comment.
Do we want to align the naming between CLI and UI (UI is marked as "example" while CLI is not)
| - [The Rationale behind kpt](guides/rationale.md) | ||
| - [Namespace provisioning example](guides/namespace-provisioning-example.md) | ||
| - [Namespace provisioning CLI](guides/namespace-provisioning-cli.md) | ||
| - [Namespace provisioning UI](guides/namespace-provisioning-ui.md) |
There was a problem hiding this comment.
I feel like removing the "example" could be confusing here：1. it seems to be the prerequisite to use Porch. 2. it's placed right after "Rationale" and before "Porch", which seems to be the second thing users should be consider (even before installing porch?)
|
|
||
| In this guide, we will use the package orchestration UI to: | ||
|
|
||
| - Register blueprint and deployment repositories |
There was a problem hiding this comment.
Suggest addling the link to tell what "blueprint", "deployment" and "repository" means here. It seems to be the term related to "repository".
|
|
||
| - Register blueprint and deployment repositories | ||
| - Create a `kpt` package from scratch in blueprint repo | ||
| - Create a deployable instance of the `kpt` package |
There was a problem hiding this comment.
do we have a doc to talk about "variant constructor"? It seems confusing especially for existing kpt users.
|
Approved since the comments are not blockers. |
|
Thanks Yuwen for the feedback. I have taken notes and will address them in the follow up PRs. |
This adds
namespace provisioning using UIguide.