kubernetes-sigs/kustomize
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kustomize.git synced 2026-05-17 18:25:26 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

2.1 release notes

Browse Source
This commit is contained in:
Jeffrey Regan
2019-05-29 16:58:34 -07:00
parent 0adfd2751e
commit e1b59c93de
2 changed files with 46 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/inventory_object.md
View File

@@ -10,10 +10,12 @@ inventory:
```
### Motivation
If present, `Kustomize build` will make an _inventory_ object,
which could be a ConfigMap, or an App(to be added),
which can be consumed by a client such as those under development in
If present, `kustomize build` will make an _inventory_ object,
which could be a ConfigMap, or an App (to be added),
which can be consumed by a client such as those under development in
[cli-experimental](https://github.com/kubernetes-sigs/cli-experimental).
The client can recognize this object by name and use it to do a better job
with actions like `apply`, `prune` and `delete`.

45
docs/v_2.1.0.md
View File

@@ -1,9 +1,44 @@
# kustomize 2.1.0
_WIP, release target date May 20 2019_
_TODO: provide details; this is just a high level list_
Lots of bug fixes since 2.0.3, and too many commits (over 300).
Summary: Go modules, inventory, plugins, eased loading restrictions.
## Go modules
Kustomize now defines it dependencies in a `go.mod` file,
and how this is used to support kustomize libraries
for use in other tools will start evolving.
## The inventory
This is an alpha feature.
Users can add an `inventory` stanza to their
kustomization file, to add a special inventory
object to the build result. This object can be
applied to the cluster and used to manage
intelligent history aware pruning.
Details [here](inventory_object.md).
## Generator and transformer plugins
Kustomize reads or creates resources, transforms
them, and emits them as YAML. The kustomization
file is a declaration of how this works.
The client can recognize this object by name and use it to do a better job
with actions like `apply`, `prune` and `delete`.
* The `inventory` field. See [inventory object](inventory_object.md).
* The `generators` and `transformers` fields.
See [plugins](plugins.md).
@@ -12,7 +47,9 @@
* Field changes / deprecations (use `kustomize fix`)
* The `resources` field generalized,
* The `resources` field generalized, can accept
what was being placed in bases.
`bases` field deprecated.
* New `envs` sub-field introduced to both