Skip to content

Commit ae610d1

Browse files
authored
Update 02-quickstart.md
1 parent 81b3c8b commit ae610d1

File tree

1 file changed

+9
-20
lines changed

1 file changed

+9
-20
lines changed

site/book/01-getting-started/02-quickstart.md

Lines changed: 9 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -57,15 +57,15 @@ $ vim deployment.yaml
5757

5858
### Automating One-time Edits with Functions
5959

60-
The `kpt fn`set of commands enable you to execute programs called _kpt functions_. These
61-
programs are packaged as containers and take in YAML files, modify or validate them, and then
60+
The `kpt fn` set of commands enable you to execute programs called _kpt functions_. These
61+
programs are packaged as containers and take in YAML files, mutate or validate them, and then
6262
output YAML.
6363

64-
For instance, you can use a function (`gcr.io/kpt-fn/search-replace:v0.1`)to search and replace all
64+
For instance, you can use a function (`gcr.io/kpt-fn/search-replace:v0.1`) to search and replace all
6565
the occurrences of the `app` key in the `spec` section of the YAML document (`spec.**.app`) and
6666
set the value to `my-nginx`.
6767

68-
You can use the `kpt fn eval` command to run this mutation on your local files a single time.
68+
You can use the `kpt fn eval` command to run this mutation on your local files a single time:
6969

7070
```shell
7171
$ kpt fn eval --image gcr.io/kpt-fn/search-replace:v0.1 -- by-path='spec.**.app' put-value=my-nginx
@@ -123,28 +123,17 @@ cluster.
123123
`kpt live` commands provide the functionality for deploying packages to a
124124
Kubernetes cluster.
125125

126-
Install the Resource Group CRD. The Resource Group CRD
127-
allows you Kpt to group resources so that they can be applied, udpated, pruned, and
128-
deleted together.
129-
130-
```shell
131-
$ kpt live install-resource-group
132-
```
133126

134-
Now, initialize the Kpt package. This adds some metadata to the `Kptfile` required to keep track of changes made
135-
to the state of the cluster. For example, if a resource is deleted from the package in the future,
136-
it will be pruned from the cluster.
127+
First, initialize the kpt package:
137128

138129
```shell
139130
$ kpt live init
140131
```
141132

142-
You can validate the resources and verify that the expected changes will be made
143-
to the cluster:
144-
145-
```shell
146-
$ kpt live apply --dry-run
147-
```
133+
This adds metadata to the `Kptfile` required to keep track of changes made
134+
to the state of the cluster. This
135+
allows kpt to group resources so that they can be applied, updated, pruned, and
136+
deleted together.
148137

149138
Apply the resources to the cluster:
150139

0 commit comments

Comments
 (0)