v0.7.0

[hvpa-controller]

🏃 Others

• [OPERATOR] The hvpa-controller container image now uses a non root user by default. (gardener/hvpa-controller#103, @dimityrmirchev)

v0.6.0

[hvpa-controller]

🏃 Others

• [USER] Fix an issue where the HVPA would set Requests higher than Limits if ControlledValues: RequestsOnly is set (gardener/hvpa-controller#98, @voelzmo)
• [OPERATOR] Published docker images for HVPA-Controller are now multi-arch ready. They support linux/amd64 and linux/arm64. (gardener/hvpa-controller#101, @timuthy)

v0.5.1

[hvpa-controller]

🏃 Others

• [USER] Fix an issue where the HVPA would set Requests higher than Limits if ControlledValues: RequestsOnly is set (gardener/hvpa-controller#99, @voelzmo)

v0.5.0

[hvpa-controller]

🏃 Others

• [OPERATOR] The HVPA controller now respects controlledResources and controlledValues parameters that have been newly introduced in autoscaling.k8s.io/v1. (gardener/hvpa-controller#93, @stoyanr)
• [OPERATOR] autoscaling.k8s.io/v1 is now being used instead of autoscaling.k8s.io/v1beta2 in HVPA resources. This enables using controlledValues: RequestsOnly in spec.vpa.template.spec.resourcePolicy (gardener/hvpa-controller#91, @stoyanr)

v0.4.0

[hvpa-controller]

⚠️ Breaking Changes

• [DEVELOPER] Switch to github.com/gardener/hvpa-controller/api if you vendor only the API of hvpa-controller. (gardener/hvpa-controller#85, @amshuman-kr)

🏃 Others

• [OPERATOR] Check if OOMKilled pod has latest resource values before overriding stabilisation (gardener/hvpa-controller#78, @ggaurav10)
• [OPERATOR] consider hpa scale out limited if hpa is not deployed (gardener/hvpa-controller#77, @ggaurav10)
• [DEVELOPER] Golang is upgraded to 1.15.3. (gardener/hvpa-controller#81, @mvladev)

📰 Noteworthy

• [OPERATOR] A new module github.com/gardener/hvpa-controller/api can be used to get the API definitions. (gardener/hvpa-controller#85, @amshuman-kr)

v0.3.1

• Check if OOMKilled pod has latest resource values before overriding stabilisation (#78)
• consider hpa scale out limited if hpa is not deployed (#77)

v0.3.0

[hvpa-controller]

Improvements

• [OPERATOR] Minor bug fix: Use vpa scale policies correctly (#73, @ggaurav10)
• [OPERATOR] Change handling of LimitsRequestsGapScaleParams: Use max of value and percentage gaps, instead of min (#72, @ggaurav10)
• [OPERATOR] Now HVPA doesn't take VPA recommendations into account if VPA condition has ConfigUnsupported, ConfigDeprecated or LowConfidence set to true (#68, @ggaurav10)
• [OPERATOR] Removing "Temporary/fast fix to enable scale down even if vpaWeight == 0" as we have better ways to optimise cost now (#64, @ggaurav10)
• [OPERATOR] Ignore minChange configuration while overriding scale up stabilisation. This ensures that full VPA recommendations are applied in case the target pods are OOMKilled or restarted due to livenessProbe failure, no matter what. (#61, @amshuman-kr)
• [OPERATOR] Consider HPA to be limited if we have seen oomkill or liveness probe fails already. This change makes HVPA controller scale the app vertically more actively, ignoring the HPA's status condition type ScalingLimited. (#57, @ggaurav10)
• [OPERATOR] Consider HPA scale out to be limited in case, overrideScaleUpStabilization is set in the status and hpa weight is 0 so that full VPA recommendation is immediately applied. (#56, @ggaurav10)
• [OPERATOR] Add ci master build status and go report card badges (#54, @ggaurav10)

v0.2.5

[hvpa-controller]

Improvements

• [OPERATOR] Removing "Temporary/fast fix to enable scale down even if vpaWeight == 0" as we have better ways to optimise cost now (#63, @ggaurav10)

v0.2.4

[hvpa-controller]

Improvements

• [OPERATOR] Ignore minChange configuration while overriding scale up stabilisation. This ensures that full VPA recommendations are applied in case the target pods are OOMKilled or restarted due to livenessProbe failure, no matter what. (#62, @amshuman-kr)

v0.2.3

no release notes available