Releases: scality/metalk8s
MetalK8s 2.7.2
MetalK8s 2.7.2 embeds Kubernetes 1.18.16.
Documentation
https://metal-k8s.readthedocs.io/en/2.7.2
Upgrade Notes
Please follow the upgrade instructions here
Changelog since 2.7.1
Full list of closed issues is available here
What’s new
- Based on Kubernetes version 1.18.16
- Improved stability for Salt master and cluster upgrade
- Properly working deployment on offline environments
MetalK8s 2.6.1
2.6.1 embeds Kubernetes 1.17.17 which is already EOL since 2021-01-13. It is recommended to upgrade to the latest MetalK8s version, using 2.6.1 as an intermediate upgrade step.
Documentation
https://metal-k8s.readthedocs.io/en/2.6.1
Upgrade Notes
Please follow the upgrade instructions here
Changelog since 2.6.0
Full list of closed issues is available here
What’s new
- Based on Kubernetes version 1.17.17
- Ability to sort Nodes list in UI
MetalK8s 2.5.2
2.5.2 embeds Kubernetes 1.16.15 which is already EOL since 2020-09-02. It is recommended to upgrade to the latest MetalK8s version, using 2.5.2 as an intermediate upgrade step since it is not possible to upgrade directly from 2.4.x to 2.6.0+ (MetalK8s only support 1 minor version upgrade at once).
Documentation
https://metal-k8s.readthedocs.io/en/2.5.2
Upgrade Notes
Please follow the upgrade instructions here
Changelog since 2.5.1
Full list of closed issues is available here
What’s new
- Based on Kubernetes version 1.16.15
- Embed CoreDNS version 1.6.2
- Embed containerd version 1.2.14
- Possibility to create raw block volumes
MetalK8s 2.7.1
WARNING: this release is missing the pause:3.2
image, which prevents offline installs/upgrades (see #3120). If this is a requirement for you, please wait until 2.7.2 or higher is released.
MetalK8s 2.7.1 embeds Kubernetes 1.18.15, with all addons (monitoring, logging, authentication) updated to the latest version available.
Note: this release fixes a critical issue from MetalK8s 2.7.0, make sure to use this version instead when upgrading from 2.6.x.
Documentation
Hosted on ReadTheDocs
Sources available here
Upgrade Notes
Please follow the upgrade instructions here.
Downgrade Notes
Please follow the downgrade instructions here.
Changelog since 2.7.0
Full list of closed issues is available here.
MetalK8s 2.6.0
2.6.0 embeds Kubernetes 1.17.14 which will be EOL in a few months or weeks. It is recommended to upgrade to 2.7.0, using 2.6.0 as an intermediate upgrade step since it is not possible to upgrade directly from 2.5.0 or 2.5.1 to 2.7.0
Documentation
Hosted on ReadTheDocs
Sources available here
Upgrade Notes
Please follow the upgrade instructions here
Downgrade Notes
Note that downgrading from 2.6.0 to 2.5.1 or 2.5.0 is not supported because of some breaking changes in the etcd cluster. Downgrading would require manual backup/restore of the etcd cluster.
Changelog since 2.5.1
Full list of closed issues is available here
What's new
MetalK8s 2.6.0 is now based on Kubernetes 1.17.14. It includes:
- a new log centralization service, aggregating Pod and journal logs into Loki. Logs can be browsed from Grafana, through new dedicated dashboards or using the Explore tab.
- the ability to configure Alertmanager and existing Prometheus rules. All details are available in Service Configurations Customization documentation
- a refined UI bringing more details about Nodes and Volumes, as well as contextual links to Metrics or Logs Grafana dashboards
- some changes to the Solution framework:
- provide your Operator (Cluster)Role(s) in a single
role.yaml
file - use the
scality/metalk8s/go/solution-operator-lib
Go module to read the configuration file for your Operator - Admin UIs are now expected to be deployed by your Operator
- provide your Operator (Cluster)Role(s) in a single
MetalK8s 2.5.1
MetalK8s 2.5.1 deploys Kubernetes 1.16.10
Important: MetalK8s 2.5.0 is affected by critical security issues, it is highly recommended to upgrade as soon as possible. More details in the changelog
Documentation
Hosted on ReadTheDocs
Sources available here
Upgrade Notes
Please follow the upgrade instructions
here.
Changelog since 2.5.0
Full list of changes is available here.
This release also includes all changes from the 2.4.4 release.
What's new
- CVE fixes for SaltStack and Grafana (see CHANGELOG, version 2.4.4)
- Improved error handling for Salt jobs in the UI
- Bump MetalK8s addons to latest stable releases
- Improve resilience for Volume provisioning
- Service configurations are henceforth upgradable
- New documentation added to expose Service configuration defaults
MetalK8s 2.4.4
Deprecation warning: 2.4.x is now deprecated and will no longer be supported after July 2020.
It is recommended to upgrade to 2.5.1 or higher versions as soon as possible.
MetalK8s 2.4.4 deploys Kubernetes 1.15.12
Documentation
Hosted on ReadTheDocs
Source available here
Upgrade Notes
Follow the upgrade instructions here.
Customizations done on MetalK8s service or deployments, such as the number of replicas for a specific service or alert rule in AlertManager, will be lost after upgrading to 2.4.4. This issue is solved starting with the 2.5.0 release.
Downgrade Notes
Warning: After upgrading to 2.4.4, downgrading requires following the manual procedure documented here.
Changelog since 2.4.3
The full list of changes is available here.
Notable fixes
- Upgrade Salt master to version 3000.3 (CVE fixes, see CHANGELOG)
- Upgrade Grafana to version 6.7.4 (CVE fix, see CHANGELOG)
- Added support for python-kubernetes v11 (compatibility with K8s 1.15)
- Improve robustness of lifecycle operations (upgrade, downgrade, expansion)
MetalK8s 2.5.0
2.5.0 Release Notes
Documentation
https://metal-k8s.readthedocs.io/en/2.5.0/
Upgrade Notes
Please follow the upgrade instructions here.
Customizations done on MetalK8s services or deployments, such as the number of replicas for specific services like Prometheus, Alertmanager and Grafana, will be lost after upgrading to 2.5.0. This issue is solved starting with this release, see instructions here.
Warning: Username and password customizations for K8s and Grafana will reset to default values once you upgrade to 2.5.0 or higher versions.
Changelog
Full list of closed issues is available here.
What's new
- MetalK8s 2.5.0 is now based on Kubernetes 1.16.8
- Rebrand of the MetalK8s UI
- Kubernetes API and Grafana are now configured to use OIDC, and Dex is
deployed to serve as their trusted Identity Provider (see here to manage Dex) - A new framework has been added to manage Services configuration, ensuring that node reboots, upgrades, downgrades or restore operations do not lead to loss of configuration (more details in the documentation)
MetalK8s 2.4.3
2.4.3 Release Notes
2.4 is now deprecated and will no longer be supported after July 2020.
It is recommended to upgrade to 2.5.0 and higher versions as soon as possible.
Documentation
https://metal-k8s.readthedocs.io/en/2.4.3
Upgrade Notes
Please follow the upgrade instructions here
Customizations done on MetalK8s service or deployments, such as the number of replicas
for a specific service or alert rule in AlertManager, will be lost after
upgrading to 2.4.3. This issue is solved starting from 2.5.0 release.
Changelog since 2.4.2
Full list of closed issues is available here
What's new
- MetalK8s 2.4.3 is now based on Kubernetes 1.15.11.
- Revamp solution lifecycle and environments as well as associated tooling.
More information is available in the documentation
MetalK8s 2.4.2
This is a maintenance release, which features:
prometheus-adapter
is deployed, enabling the usekubectl top
among others- host-local
nginx
on every node to provide HA access tokube-apiserver
- documentation access from the UI
- safer
etcd
expansions