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

CORTX K8s Release v0.10.0

Compare
Choose a tag to compare
@walterlopatka walterlopatka released this 16 Aug 00:29
· 37 commits to integration since this release
7a920e1

The latest released code v0.10.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-895
ghcr.io/seagate/cortx-rgw:2.0.0-895
ghcr.io/seagate/cortx-control:2.0.0-895

Key changes:

  • F-26C: Highly Available cortx-control pods:
    • In Helm chart, specify control.replicaCount to create multiple cortx-control pods. (Default is 1 replica, which is no change from previous.)
    • This change also allows failed cortx-control pods to be replaced on any node (not bound to a single node)
    • See the description of CORTX-32842 for detailed instructions.
  • CORTX-33135: Verbose K8s logging for cortx-control containers
    • By specifying global.cortx.setupLoggingDetail = “all” (or “component”) in values.yaml, all lines logged to various log files internal to the container are sent to stdout so that they are readily accessible via kubectl logs.
    • (More fine-grained logging options are also available. See github README for details.)
  • CORTX-33749: Workaround for conntrack table issues
    • One source of IO stability has the symptom of “connection resets” on stressful workloads.
    • Saurabh identified the problem earlier. This fix implements the solution as part of prereq-deploy-cortx-cloud.sh plus accompanying documentation.
    • (Technically this is not a CORTX/K8s issue, but is a configuration that must be present in the environment.)
  • CORTX-27411: Add global image options
    • In Helm chart, allow general image pull policy, registration, and tag to be specified in a single, global location (rather than repeated with each image)

What's Changed

Full Changelog: v0.9.0...v0.10.0