v0.7.2

no release notes available

v0.7.1

[dependency-watchdog]

🐛 Bug Fixes

• [OPERATOR] A bug is fixed which allowed dependency-watchdog to not ignore scaling operations on deployment which are not enabled/deployed in a given cluster (gardener/dependency-watchdog#46, @acumino)
  • A bug with uploading of a rotated dependency-watchdog-probe secrets is now fixed by refreshing the clients with updated secrets.

📰 Noteworthy

• [OPERATOR] A dependent's scaling up/down can be ignored by DWD now by adding the annotation dependency-watchdog.gardener.cloud/ignore-scaling to the deployment (gardener/dependency-watchdog#49, @himanshu-kun)

v0.7.0

[dependency-watchdog]

✨ New Features

• [DEVELOPER] Export types in pkg/restarter and pkg/scaler to make them reusable for other packages. (gardener/dependency-watchdog#33, @rfranzke)

🏃 Others

• [OPERATOR] Operators can now provide a scaleUpDelaySeconds or|and scaleDownDelaySeconds for individual dependent resources for dependency-watchdog probe to consider while scaling. (gardener/dependency-watchdog#39, @ashwani2k)
  • In addition to the delay, for each resource managed by dependency-watchdog probe one can also specify additional dependent resources via a new field scaleRefDependsOn. This ensures that dependency-watchdog probe applies scaling operation on a resource only if the dependents for this resource defined under scaleRefDependsOn are available in the desired state as per the applicable scaling operation.
• [OPERATOR] Switch default leader election resource lock for dependency-watchdog from endpoints to endpointsleases (gardener/dependency-watchdog#37, @ary1992)
• [OPERATOR] Fix panic during shoot spec and status check. (gardener/dependency-watchdog#28, @amshuman-kr)
• [DEVELOPER] Enhance package structure to isolate APIs (gardener/dependency-watchdog#34, @rfranzke)

📰 Noteworthy

• [DEVELOPER] License and copyright information is now specified in REUSE format. (gardener/dependency-watchdog#31, @msohn)

v0.6.1

[dependency-watchdog]

Improvements

• [OPERATOR] Fix panic during shoot spec and status check. (#29, @amshuman-kr)

v0.6.0

[dependency-watchdog]

Improvements

• [OPERATOR] Improve logging while scaling. (#24, @amshuman-kr)
• [OPERATOR] Probe is stopped for clusters that are hibernating, or in hibernation or are still waking up from hibernation (#23, @ggaurav10)

v0.5.0

[dependency-watchdog]

Improvements

• [OPERATOR] Minimize throttling for happy path of probes (when targets do not need to be updated). (#20, @amshuman-kr)
  • For example, load the current replicas via the local cache, add jitter to the probe intervals to spread out host apiserver call, make client-go QPS and Burst configurable via CLI flags and export load-related metrics.

v0.4.1

[dependency-watchdog]

Most notable changes

• [USER] Fixed the command-line incompatibility for the root command introduced in the release 0.3.0. (#8, @amshuman-kr)

Improvements

• [OPERATOR] Probes are now restarted only if any of the target kubeconfigs actually changed. Also, the kubeconfig secrets are loaded from the informer rather than hitting the host apiserver (seed) with GET calls. Also, logged OS signal for debugging. (#16, @amshuman-kr)
• [OPERATOR] Log flags and configuration. (#13, @amshuman-kr)
• [OPERATOR] The release tags from now are prefixed with v. (#11, @ialidzhikov)

0.4.0

[dependency-watchdog]

Most notable changes

• [USER] Fixed the command-line incompatibility for the root command introduced in the release 0.3.0. (#8, @amshuman-kr)

0.3.0

[dependency-watchdog]

Most notable changes

• [USER] Introduced cobra commands. (#7, @amshuman-kr)
  • 1. The root command works exactly like before.
  • I.e. it watches the endpoint objects and kicks the
  • dependant pods in CrashloopBackoff.
  • 2. The probe sub-command probes kube-apiservers
  • using internal and external IP kubeconfigs and
  • scales the dependant scale subresources up and down.
  • Both the root command and the probe sub-command support
  • managing a single namespace as well as all namespaces.

0.2.0

[dependency-watchdog]

Improvements

• [OPERATOR] Enabled the dependency-watchdog to have hierarchy of service-pod dependency. (#6, @georgekuruvillak)