4
4
actuation of Kubernetes resource objects by wraping and enahancing
5
5
` kubectl apply ` with a more user friendly abstraction.
6
6
7
- While the name incidates a focus on CLI utilities, the project has evolved to
7
+ While the name indicates a focus on CLI utilities, the project has evolved to
8
8
encompass a broader scope, including CLI use and server-side use in GitOps
9
9
controllers.
10
10
@@ -28,11 +28,11 @@ removed from the input set on a subsequent apply.
28
28
29
29
The current implementation of ` kubectl apply --prune ` uses labels to identify the
30
30
set of previously applied objects in the prune set calculation. But the use of labels
31
- has significant downsides. The current ` kubectl apply --prune ` implemenation is alpha,
31
+ has significant downsides. The current ` kubectl apply --prune ` implementation is alpha,
32
32
and it is improbable that it will graduate to beta. ` cli-utils ` attempts to address
33
33
the current ` kubectl apply --prune ` deficiencies by storing the set of previously
34
34
applied objects in an ** inventory** object which is applied to the cluster. The
35
- reference implimentation uses a ` ConfigMap ` as an ** inventory** object, and references
35
+ reference implementation uses a ` ConfigMap ` as an ** inventory** object, and references
36
36
to the applied objects are stored in the ` data ` section of the ` ConfigMap ` .
37
37
38
38
The following example illustrates a ` ConfigMap ` resource used as an inventory object:
@@ -66,7 +66,7 @@ is expected to never reconcile (aka Failed).
66
66
67
67
# ## Status Lookup
68
68
69
- In addition to performing interpritation of status from an object in-memory,
69
+ In addition to performing interpretation of status from an object in-memory,
70
70
` cli-utils` can also be used to query status from the server, allowing you to
71
71
retrieve the status of previously or concurrently applied objects.
72
72
@@ -75,7 +75,7 @@ retrieve the status of previously or concurrently applied objects.
75
75
` cli-utils` can be used to compare local object manifests with remote objects
76
76
from the server. These can be compared locally with diff or remotely with
77
77
preview (aka dry-run). This can be useful for discovering drift or previewing
78
- which changes would be made, if the loal manifests were applied.
78
+ which changes would be made, if the local manifests were applied.
79
79
80
80
# ## Waiting for Reconciliation
81
81
@@ -84,7 +84,7 @@ status, blocking until the objects have reconciled, failed, or been fully
84
84
deleted.
85
85
86
86
This functionality is similar to `kubectl delete <resource> <name> --wait`, in
87
- that is waits for all finalizers to complete, except it also works for creates
87
+ that it waits for all finalizers to complete, except it also works for creates
88
88
and updates.
89
89
90
90
While there is a `kubectl apply <resource> <name> --wait`, it only waits for
@@ -168,7 +168,7 @@ to seperate into multiple sets, with manual modifications between applies.
168
168
Apply-Time Mutation is configured using the
169
169
` config.kubernetes.io/apply-time-mutation` annotation on the target object to be
170
170
modified. The annotation may specify one or more substitutions. Each
171
- substitution inncludes a source object, and source field path, and a parget
171
+ substitution includes a source object, and source field path, and a target
172
172
field path, with an optional token.
173
173
174
174
If the token is specified, the token is
@@ -228,7 +228,7 @@ interfaces, or creating dependencies between otherwise independent interfaces.
228
228
# ## CLI Printers
229
229
230
230
Since the original intent of `cli-utils` was to contain common code for CLIs,
231
- and end-to-end testing requires a reference implimentation , a few printers are
231
+ and end-to-end testing requires a reference implementation , a few printers are
232
232
included to translate from the primary event stream into STDOUT text :
233
233
234
234
1. **Event Printer** : The event printer just prints text to STDOT whenever an
@@ -250,7 +250,7 @@ included to translate from the primary event stream into STDOUT text:
250
250
│ ├── **config** : inventory config bootstrapping
251
251
│ ├── **errors** : error printing
252
252
│ ├── **flowcontrol** : flow control enablement discovery
253
- │ ├── **inventory** : inventory resource reference implimentation
253
+ │ ├── **inventory** : inventory resource reference implementation
254
254
│ ├── **jsonpath** : utility for using jsonpath to read & write Unstructured object fields
255
255
│ ├── **kstatus** : object status event watcher with ability to reduce status to a single enum
256
256
│ ├── **manifestreader** : bolk resource object manifest reading and parsing
0 commit comments