v0.5.4

Fixed template function calls with varargs

v0.5.3

Added more template functions

v0.5.2

1. metadata.resourceVersion for all resources

v0.5.1

Implemented more checks for namespace requirements

v0.5.0

1. Update to latest versions of kubernetes, docker, ...
2. Enable ignoring of schema validation for specified GVK

v0.4.11

1. Change envar KUBOR_KUBECONFIG to simply KUBECONFIG.
2. If kubeconfig="mock" and context="" set context=mock, too.

v0.4.10

Ignore requirement of namespace if kind is namespace.

v0.4.9

Changed organization from levertonai to echocat

v0.4.8

Fixes

#8 An issue where while applying new configurations kubor reported instantly the success - also if the target pods are not already fully up.

v0.4.7

Improvements

1. Keep Alive for applying new stuff.
   On an apply command kubor is waiting that the applied resources are ready (means usually that all required readinessProbes are up). This requires a watch request against the Kubernetes API Server. Sometimes this server could be behind a load balancer (like an AWS ELB). This load balancers sometimes are dropping connections when the connection is idle for some time. If in this amount of time the event of ready appears the deployment could stuck or is aborted. This new functionality of kubor is dealing with this behavior by redo the watch every 60 seconds (configurable via --keepAlive=<duration> or env KUBOR_KEEP_ALIVE=<duration>).

Fixes

1. Sometimes the status of deployments are assumed as ready also if they are not ready. This was caused by the fact that an empty status was assumed as ready. Now an empty status is assumed as not ready.

New features

1. Now kubor is able to wait for the success also of single Pods.