CORTX Services Release v0.0.16

The following changes have been made for this release:

• v0.0.15, SNS Validation failing [UDX-6790]
• Convert Provisioner Pods to initContainers [UDX-6718]
• Setting the max_map_count persistent across reboots [UDX-6765]
• To get machine-id in pod metadata label named "machineid" [UDX-6746]

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.15

The following changes have been made for this release:

• prereq-deploy-cortx-cloud.sh doesn't install Helm [UDX-6562]
• Allow for multiple CORTX deployments with different namespaces in the same cluster [UDX-6041]
• Validation required for solution.yaml in Services Framework If any field is missing [UDX-6520]
• 3rd Party Issue causing Data pod status stuck at Container Creating After ~3 Hrs of IO [UDX-6654]
• Remove gluster from deployment [UDX-6607]
• Block storage should only be connected to the io service [UDX-6647]
• Tool/Document for logs to be collected for deployment failure [UDX-6655]
• Support Bundle tarfiles are not included in final tarball generated by Log Collector [UDX-6642]
• Third-party docker images should be fetched from local & secured container registries [UDX-6442]
• mitigate kubescape results [UDX-6512]
• ./logs-cortx-cloud.sh fails if not launched from the same directory with parse_scripts [UDX-6723]
• Add 'common>release' key in configmap(config.yaml) file [UDX-6755]

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.14

The following changes have been made for this release:

• Default "log" path should be local PVC [UDX-6603]

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.13

The following changes have been made for this release:

• Rancher image location not passed to the template
• DNS resolution is not occurring with headless services before all the containers are ready [UDX-6533]
• Initial Log collection script available [UDX-6059] See jira comment to usage details

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.12

The following changes have been made for this release:

• Removed deploy / destroy 3rd party scripts to avoid confusion when the releasing to external users
• Updates to prereq, deploy and destroy scripts to make them more structured
• prereq no longer pulls the docker images. This should be done manually as it is not required in real deployments
• prereq no longer needs the full repo copied to each worker node. Only the script and solution are required
• Removed unused cortx_io_svc_ingress service
• Improvements required following CORTX setup in AWS [UDX-6481]
• Disable 3rd party pods which are not required for CORTX [UDX-6501]
• Adoption of new symas OpenLDAP image in cortx-services script [UDX-6507]
• Skip Replication in OpenLDAP for single node setup [UDX-6506]
• destroy-cortx-cloud.sh script should support --force option [UDX-6472]
• Kafka pod stuck in pending state on 3N deployment [UDX-6415]
• kafka-1 POD issues(Restarts/Error/Connection) while deploying and deployment aborted due to timeout [UDX-6513]
• All data POD went into CrashLoopBackOff post successful deployment of 12-Node Cluster [UDX-6497]
• Adding max_start_timeout in solutions config file [UDX-6522]

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.11

The following changes have been made for this release:

• Only one LoadBalancer service is created for cortx data pod [UDX-6474]
• Not able to access CSM endpoint using IP with new Load balancer services [UDX-6473]
• Glusterfs deploy failed [UDX-6471]
• destroy-cortx-cloud.sh script should support --force option [UDX-6472]

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.10

The following changes have been made for this release:

• CSM Agent endpoint port should be fixed [UDX-6458]
• Loadbalancer services are missing configuration for External ips [UDX-6440]
• Enable log rotation for OpenLDAP [UDX-6375]
• Deployment script stuck when Error occurs in cortx-control-provisioner-pod [UDX-6463]
• Deployment script continues when Error occurs in applying Secrets [UDX-6464]
• Space is getting full on one node because all the logs are residing only one node [UDX-6466]

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.9

The following changes have been made for this release:

• Helm charts work with both "dummy" and "CORTX ALL" containers. If image is centos:7 helm runs in "dummy" mode any other name runs "CORTX ALL" mode. See README.txt for details
• CORTX ALL images ghcr.io/seagate/cortx-all:2.0.0-latest-custom-ci are now default for containers
• Added solution_dummy.yaml for testing with dummy containers
• Added VERSION file to cortx-k8s/k8_cortx_cloud
• Updates to the status script to check PVCs and PVs

Note: By default, all scripts use solution.yaml which uses the CORTX ALL images. To use dummy container, call the scripts with and pass the solution_dummy.yaml file as the first argument.

CORTX Services Release v0.0.8

The following changes have been made for this release:

• Updated README.txt for preq and state that it should be run on all worker node in the cluster [UDX-6444]
• Added specific version tags for 3rd party [UDX-6411]
• Changed control nodeport service to be a loadbalancer service
• Changed solution.nodes.nodeX.devices.system to be solution.common.storage_provisioner_path in preparation for configurable provisioner path
• Allow configuration of the solution.common.storage_provisioner_path

CORTX Services Release v0.0.7

The following changes have been made for this release:

• Take solution.yaml as input for deploy-cortx-cloud.sh and destroy-cortx-cloud.sh [UDX-6412]
• unmount system drive if it's already mounted [UDX-6410]
• Use fixed third-party component image tag instead of latest [UDX-6411]
• Glusterfs shared volume is getting full and not getting cleaned up [UDX-6435]
• Initial versions of shutdown, start and status scripts. WORK IN PROGRESS [UDX-6042]