Skip to content

Releases: kuberhealthy/kuberhealthy

v2.8.0-rc2

03 Jan 08:46
Compare
Choose a tag to compare
v2.8.0-rc2 Pre-release
Pre-release

What's Changed

  • go mod updates to resolve segfaults in multi-arch builds by @integrii in #1178
  • disable tests on releases because they case segfaults by @integrii in #1179
  • move away from unstructured watcher by @integrii in #1180

Full Changelog: v2.8.0-rc1...v2.8.0-rc2

v2.8.0-rc1

23 Dec 06:31
6c9dac2
Compare
Choose a tag to compare
v2.8.0-rc1 Pre-release
Pre-release

Test release to test the new deployment github workflow

v2.7.1

25 Apr 04:47
4b49980
Compare
Choose a tag to compare

This release mostly contains minor fixes and documentation. Special thanks to @Hungrylion2019 this release. Thank you for all your help!

If your business uses Kuberhealthy, please take a moment to add it to the adopters list! This helps us advance through the ranks of the CNCF.

What's Changed

New Contributors

Full Changelog: v2.7.0...v2.7.1

v2.7.0

30 Jul 22:58
45e156a
Compare
Choose a tag to compare

Version v2.7.0 raises the minimum supported version of Kubernetes to 1.16.

  • Fixes for checks failing to create khstate resources #988. (@jonnydawg)

v2.6.0

16 Jul 17:27
7ac3262
Compare
Choose a tag to compare

For this v2.6.0 release, apply the newly generated CRDs:

  • KuberhealthyCheck
  • KuberhealthyJob
  • KuberhealthyState

Bug Fixes:

  • Fixing prometheus rules integration for operator and additionalLabels #962 @skuethe
  • Remove Comcast mentions #969 @integrii
  • Reaper NPE bug - ensure container terminated state exists before fetching container terminated time #970 @joshulyne
  • Set owner references only on pods in the kuberhealthy namespace #903, PR #973 @mikeinton
  • Add missing namespace metadata to helm chart configmap #976, PR #977 @integrii

New Features:

  • Generate and update kuberhealthy crds #778, PR #937 @joshulyne
    • Include node that checks ran on in khstate data #351

v2.5.0

27 May 18:39
5e27b32
Compare
Choose a tag to compare

Kuberhealthy v2.5.0

Bug Fixes:

New Features:

  • Kuberhealthy has been accepted into the CNCF Sandbox 🎉
  • Migration from Comcast github organization to its own (https://github.com/kuberhealthy) 🎉
  • Added optional support for Kuberhealthy pod affinity/antiaffinity - PR #909, @AshutoshNirkhe
  • Added namespace to pod status error messages - PR #902, @rawlingsj
  • Added option to install pod restart checks at the cluster scope - PR #897, @rawlingsj
  • Refactored external report validation to use check run uuid, but maintain support for also using pod IP validation PR #884, @joshulyne, @integrii
  • Refactor config options for checkReaper: maxKHJobAge, maxCheckPodAge, maxCompletedPodCount, maxErrorPodCount and allow for 0 pod count values or the option to have no completed pods lying around - PR #884, @joshulyne, @integrii
  • Up minor versions on all checks to use new checkClient package #944 @mikeinton

v2.4.1

14 Apr 22:31
46934bb
Compare
Choose a tag to compare

Kuberhealthy v2.4.1

Bug Fixes:

  • Fix for retries when updating the kuberhealthy run UUID on the khstate resource - #858, PR #872 @integrii
  • Fix checkReaper duration configs, add failedPodCleanupDuration making it configurable, re-enable unit tests for kuberhealthy - #857, #859, #861, PR #862 @joshulyne
  • Edit prometheus operator installation instructions; fix grafana prometheus datasource - #848, #850 @joshulyne
  • Set proper pod port where prometheus metrics are exposed - PR #869 @randrusiak
  • Pod-restarts check - fixed updating errorMessages with err, fixed pod-restarts-check rbac role to be able to list events - #828, PR #829 @isaaguilar

New Features:

  • Complete refactor of ssl_util package for ssl-hanshake check - #879 @integrii

New Kuberhealthy Check:

v2.4.0

04 Feb 19:06
1b5d0c6
Compare
Choose a tag to compare

Kuberhealthy 2.4.0

Upgrade Instructions:

When upgrading to this release, you should expect to see the check-reaper cronjob be removed. This functionality is now present in the main Kuberhealthy binary/pod. If you deployed via helm template, you must manually remove the check-reaper cronjob and its associated RBAC. This should happen automatically if you used helm install.

Changes and Fixes

v2.3.2

22 Jan 20:56
8fd9f98
Compare
Choose a tag to compare

Kuberhealthy 2.3.2

Upgrade Instructions:

  • When upgrading to this release, you must be sure the khjob custom resource is applied in your cluster. Without this, the check reaper will crash. If you use the Helm chart, this will be done for you automatically.

Features:

Bug Fixes:

  • Added ACTIONS_ALLOW_UNSECURE_COMMANDS env var to fix deprecated GitHub 'add path' action. #727, #729 @jonnydawg
  • Added check-reaper ClusterRole to fix permissions issue. #732, #737 @joshulyne
  • Updated invalid, legacy URL in Helm chart. #736, #738 @TJM
  • Removed nodecheck WaitForKubeProxy for clusters not using kube-proxy, and modified WaitForNodeAge to pass in nodeName using downward API instead of needing additional permissions to get nodeName information. #739, #752, #755 @joshulyne
  • Set default PASSING_PERCENT for http-check. #768, #780 @jdowni000

v2.3.1

05 Nov 21:21
1050686
Compare
Choose a tag to compare

Kuberhealthy 2.3.1

Bug Fixes:

  • Manually set KH_EXTERNAL_REPORTING_URL environment variable is now properly processed and respected #715 @zjhans
  • ConfigMap with Prometheus rules had been deprecated, updated to be properly picked up #718 @linkvt
  • The whitespace between both ConfigMaps was chomped, causing the ConfigMaps to merge, this has been fixed. #718 @linkvt