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

v0.9.0

Compare
Choose a tag to compare
@walterlopatka walterlopatka released this 20 Jul 23:48
· 57 commits to integration since this release
910e57e

The latest released code v0.9.0 from CORTX Services is available at https://github.com/Seagate/cortx-k8s on the main branch. This release has been verified with:
ghcr.io/seagate/cortx-data:2.0.0-871
ghcr.io/seagate/cortx-rgw:2.0.0-871
ghcr.io/seagate/cortx-control:2.0.0-871

This is a major release that includes multiple data pods per node and refactored Helm charts. Note that the solution.example.yaml format has changes that are not compatible with previous versions.

Key changes:

  • F-87I: Multiple data pods per node: With multiple CVGs defined in the storage section, multiple cortx-data pods will be created (see below or cortx-k8s/README.md for details)
  • F-87J: Helm Chart Refactor: Though changes in solution.yaml are minor, the Helm charts that implement CORTX deploy have undergone a major refactoring. The most significant effect from a user perspective is that all K8s resources are created at once and then transition to ready dependencies are resolved. Besides a significant reduction in deploy complexity, this also allows CORTX to deploy faster.

Other changes:

  • CORTX-32355: Increase Consul default resources
  • CORTX-33050: Add support for Motr log devices (not yet supported in motr)
  • CORTX-33598: Updated max namespace length to 20 characters
  • CORTX-31831: Probes to avoid initial Kafka restarts
  • CORTX-29838: Fix containerPort off-by-one
  • number of cortx-server pods is configurable via the solution.common.s3.instances_per_node setting. (default=1)

Key Changes in solution.yaml file
The primary change is the structure of the storage_sets section:

  • “nodes” now specifies a simple list of worker nodes to deploy cortx on
  • “storage” is a list of CVGs.
    • CVGs will be deployed across multiple pods, as determined by the number of CVGs and the “container_group_size” setting. If container_group_size is 1, then each CVG is deployed as a separate cortx-data StatefulSet / Pod.
    • Format of metadata and data sections is slightly different. See solution.example.yaml.
  • The “storage_sets” section is now formatted as a list, even though CORTX at this time supports only a single storage set.

What's Changed

New Contributors

Full Changelog: v0.8.0...v0.9.0