Skip to content
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.

Releases: gravitational/gravity

Release 6.1.35

17 Aug 18:08
f706a3a
Compare
Choose a tag to compare

6.1.35 LTS (August 17th, 2020)

Bugfixes

  • Fix an issue with building cluster images that use custom planet containers (#2015).

Release 6.1.34

14 Aug 18:02
bfe9dbd
Compare
Choose a tag to compare

6.1.34 LTS (August 14th, 2020)

Improvements

  • Upgrade agents will now restart automatically if nodes reboot during upgrade (#1952).
  • Add ability to display deployed agent status using gravity agent status command (#1952).
  • Update gravity plan resume command to launch from a systemd service by default, --block flag is supported for old behavior (#1935).
  • Add ability to follow operation plan using gravity plan --tail command (#1935).

Bugfixes

  • Fixes an issue with upgrades when using alternate install location (#2010).
  • Fix an issue with log forwarding configuration breaking during upgrade (#1973, logging-app#68).
  • Fix several issues with using custom planet containers (#1962).

Release 5.5.51

12 Aug 05:18
202d829
Compare
Choose a tag to compare

5.5.51 LTS (August 12th, 2020)

Bugfixes

  • Backport upstream kubernetes fix for CVE-2020-8558 to Kubernetes 1.13 (#1998, planet#650).
  • Fix an issue with log forwarding configuration breaking during upgrade (#1972, logging-app#67).
  • Fix an issue with kubernetes scheduler priorities on cluster dns app (#1991).
  • Fix an issue with etcd shutdown phase during upgrades (#1980, planet#718).
  • Fix an issue with teleport when rotating all master servers within the cluster (#1970).

Warning

This release fixes a security vulnerability in Kubernetes. Please see Kubernetes Announcement for more information.

Release 7.0.14

07 Aug 15:54
2ebca97
Compare
Choose a tag to compare

7.0.14 LTS (August 7th, 2020)

Improvements

  • Monitoring application has been updated to version 7.0.3 (#1893), (#183).
  • New command to collect gravity execution history (#1861).
  • Add kernel version test to satellite (#1926), (#250), (#713).
  • Update gravity plan resume command to launch from a systemd service by default, --block flag is supported for old behavior (#1936).
  • New command to observe status of remote agents (#1956).
  • Support for intermediate upgrades (#1920), (#714).

Bugfixes

  • Rotate RPC credentials on cluster upgrade ([#1749])(#1749)).
  • Allow execution of upload script from external directories (#1892).
  • Fix an issue with installer failing when a directory for mountpoint does not exist (#1958), (#252).
  • Update ClusterConfiguration resource to properly support service CIDR changes (#1975), (#722).

Release 5.5.50 LTS

01 Aug 00:33
b34bd36
Compare
Choose a tag to compare

5.5.50 LTS (July 31st, 2020)

Improvements

  • Gravity debug report will now include gravity CLI command history (#1858, #1895).
  • Improve gravity status performance in case of many namespaces/services (#1869).
  • Improve error messages when some Teleport nodes are unavailable prior to upgrade (#1874).
  • Update gravity plan resume command to launch from a systemd service by default, --block flag is supported for old behavior (#1899).
  • Add ability to follow operation plan using gravity plan --tail command (#1899).
  • Gravity will now report a warning if installed kernel is older than the recommended 3.10.0-1127 version (#1919, planet#708, satellite#249).
  • Gravity will now check tiller server health prior to upgrade (#1916).
  • Add ability to update Teleport auth servers using gravity system teleport set-auth-servers command (#1944).
  • Upgrade agents will now restart automatically if nodes reboot during upgrade (#1951).
  • Add ability to display deployed agent status using gravity agent status command (#1951).

Bugfixes

  • Fix an issue with InfluxDB continuous queries resulting in max series limit exhaustion (#1838).
  • Fix an issue with kube-dns resources potentially remaining when upgrading from 5.2 (#1865).
  • Fix an issue with creating custom rollups (#1896).

Release 6.1.32

29 Jul 01:43
3548a99
Compare
Choose a tag to compare

6.1.32 LTS (July 28th, 2020)

Improvements

  • Remove the hard limit of 3 master nodes. (#1910).
  • Improved warnings when teleport nodes are using the wrong join token (#1902).
  • Collect gravity cli history for debug reports (#1860).

Bugfixes

Release 7.0.13

16 Jul 00:51
345fa63
Compare
Choose a tag to compare

7.0.13 LTS (July 15th, 2020)

Improvements

  • Pull only required packages during join (#1862).

Bugfixes

Warning

This release fixes a security vulnerability in kubernetes. Please see Kubernetes Announcement for CVE-2020-8557 and Kubernetes Announcement for CVE-2020-8559 for more information.

Release 6.1.31

13 Jul 21:03
f5106bd
Compare
Choose a tag to compare

6.1.31 LTS (July 13th, 2020)

Bugfixes

  • Fix a regression in 6.1.30 that led to installation crashing in bare-metal mode during package configuration phase (#1864).

Release 7.0.12

10 Jul 20:38
8a1dbd9
Compare
Choose a tag to compare

7.0.12 LTS (July 10th, 2020)

Improvements

  • Update gravity status to display unhealthy critical system pods (#1753, planet#691, satellite#236).
  • Add --since flag to gravity report command to allow filtering collected logs by time (#1806).
  • Add more system information collectors to gravity report (#1806).
  • Set priority classes on critical system pods (#1814, logging#66, monitoring#181).
  • Update etcd disk check to produce a warning on soft limits (50ms latency, 50 IOPS) and a critical failure on hard limits (150ms latency, 10 IOPS) (#1847).

Bugfixes

  • Make sure upgrade is resumed on the correct node to avoid issues with plan inconsistency (#1794).
  • Make sure upgrade can't be launched if the previous upgrade wasn't completed or fully rolled back (#1803).
  • Fix an issue with upgrade failing to adjust volume permissions if only uid is specified (#1803).
  • Fix an issue with some tabs not working when accessed through wizard installer user interface (#1815).
  • Fix an issue with installation failing on Vultr (#1815).
  • Fix an issue with installed Helm releases not displayed on the dashboard (#1815).
  • Fix an issue with signup/reset links not honoring configured public address (#1815).
  • Fix an issue with tsh sometimes producing access denied errors (#1836).

Release 6.1.30

10 Jul 20:38
3aa47ca
Compare
Choose a tag to compare

6.1.30 LTS (July 10th, 2020)

Improvements

  • Disk space check will now trigger a warning on soft limit (80%) and degrade the node on hard limit (90%) (#1690, planet#678, #228).
  • Add backoff after new cluster image upload to make sure cluster is healthy (#1709).
  • Display a more detailed reason for degraded status in gravity status (#1723).
  • Update gravity status to display unhealthy critical system pods (#1752, planet#690, satellite#235).
  • Upgrade Grafana to v6.7.4 (#1754, monitoring#177).
  • Add --since flag to gravity report command to allow filtering collected logs by time (#1800).
  • Add more system information collectors to gravity report (#1800).
  • Update ClusterConfiguration resource to support service CIDR changes (#1839).

Bugfixes

  • Fix an issue with monitoring app upgrade sometimes failing with "request too large" (#1697, monitoring#174).
  • Fix an issue with kube-apiserver sometimes entering failed state during failover (#1742, planet#685).
  • Fix an issue with calculating port differences when upgrading to a new version (#1745).
  • Fix an issue with RPC agent credentials not being rotated during upgrade (#1747).
  • Make sure upgrade is resumed on the correct node to avoid issues with plan inconsistency (#1793).
  • Make sure upgrade can't be launched if the previous upgrade wasn't completed or fully rolled back (#1802).
  • Fix an issue with upgrade failing to adjust volume permissions if only uid is specified (#1802).