Skip to content

Commit

Permalink
Remove references to kpt live preview in the book (#2143)
Browse files Browse the repository at this point in the history
* Remove references to kpt live preview in the book

* Addressed comments
  • Loading branch information
mortent committed Jun 4, 2021
1 parent 2aeede6 commit 0d316e0
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 4 deletions.
2 changes: 1 addition & 1 deletion site/book/02-concepts/00.md
Expand Up @@ -46,6 +46,6 @@ That's a pretty terse description, so let's break it down:

- **Applying**: When it comes to deploying a package to a Kubernetes cluster, kpt complements
`kubectl`. By keeping an inventory of deployed resources, kpt enables resource pruning, aggregated
status and observability, and an improved preview experience.
status and observability, and an improved dry-run experience.

The two fundamental concepts in kpt are packages and functions. Let's define them.
7 changes: 4 additions & 3 deletions site/book/02-concepts/02-workflows.md
Expand Up @@ -46,12 +46,13 @@ may look like this:
![img](/static/images/lifecycle/flow3.svg)

- **Initialize**: One-time process using `kpt live init`
- **Preview**: Using `kpt live preview`
- **Preview**: Using `kpt live apply --dry-run`
- **Apply**: Using `kpt live apply`
- **Observe**: Using `kpt live status`

First, you preview deployment of the package to the cluster. Then if the preview looks good,
you apply the package. Afterwards, you may observe the status of the package on the cluster.
First, you use dry-run to validate the resources in your package and verify that the expected
resources will be applied and pruned. Then if that looks good, you apply the package. Afterwards,
you may observe the status of the package on the cluster.

You typically want to store the package on Git:

Expand Down

0 comments on commit 0d316e0

Please sign in to comment.