Releases: utilitywarehouse/kube-applier
Releases · utilitywarehouse/kube-applier
2.4.2
2.4.1
2.3.12
2.2.9
2.4.0
The highlight of this release is the removal of kube-applier.io/prune-whitelist
and the default whitelist in favour of retrieving the list of resources to prune dynamically from the API server. This means that all resources created by kube-applier will be pruned, rather than just an arbritrary list.
You can blacklist resource types you don't want to prune by setting PRUNE_BLACKLIST
.
If you previously weren't setting kube-applier.io/prune-whitelist
and were using the default whitelist, you may want to run with DRY_RUN=true
at first so you can examine any new resources it's going to prune and double check that they aren't used anywhere important.
Other changes:
- The
SERVER
environment variable has been removed in favour of the default kube config loading order. This means you can useKUBECONFIG
to configure the kube client - go 1.14 (ce73504)
- Templates and static resources are now served from relative paths, which makes building and running kube-applier outside of docker easier for local development (6aadf56, 9695e0a)
- Namespace annotations are retrieved using kubernetes client-go, rather than kubectl (#107)
- A new metric,
last_run_timestamp_seconds
, tracks the last time an apply run finished (#110) - kube v1.17.3 (#112)
- kustomize v3.5.4 (#113)
2.3.11
2.3.10
2.3.9
2.3.8
- Adds a new annotation,
kube-applier.io/prune-whitelist
, which can overwrite the default list of pruned resources (2ed0880) - Fixes a bug where
:
in kubectl output wasn't being parsed correctly (6ca40c3) - Fixes an issue where kustomize zombie processes were left for every run of every namespace (4233bc9)
- Tweaks the logging when waiting for the source directory to exist (0f73c5e)