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

v0.8 Merge #300

Merged
merged 4 commits into from
Jun 25, 2022
Merged

v0.8 Merge #300

merged 4 commits into from
Jun 25, 2022

Conversation

walterlopatka
Copy link
Contributor

@walterlopatka walterlopatka commented Jun 24, 2022

Description

v0.8.0 release, which delivers two changesets from the integration branch (via cherry-pick)
Also the latest cortx image version is used (837)

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds new functionality)
  • Breaking change (bug fix or new feature that breaks existing functionality)
  • Third-party dependency update
  • Documentation additions or improvements
  • Code quality improvements to existing code or test additions/updates

Applicable issues

  • This change fixes an issue:
    CORTX-32320
    CORTX-32063

CORTX image version requirements

NA

How was this tested?

  • Ran cortx-k8s regression tests
  • Ran basic S3 IO

Checklist

  • The change is tested and works locally.
  • New or changed settings in the solution YAML are documented clearly in the README.md file.
  • All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change requires newer CORTX or third party image versions:

  • The image fields in solution.example.yaml have been updated to use the required versions.
  • The appVersion field of the Helm chart has been updated to use the new CORTX version.

If this change addresses a CORTX Jira issue:

  • The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

View rendered README.md

walterlopatka and others added 4 commits June 24, 2022 16:32
…292)

* Update README.md to explain that specifying any image causes
  all three CORTX images to be pulled.

* Update -h help for upgrade-cortx-cloud.sh to explain the same

* Update README.md to describe how to update a single deployment
  or statefulset only.

Signed-off-by: Walter Lopatka <[email protected]>
Run the log gathering process for each pod in parallel.
This is needed especially for the "support_bundle generate"
calls, which can take more than 2 minutes for cortx-data pods.

The key change here is that code was refactored so that all log
collection (including support bundle generation) for a single pod
is moved to one function, and now that function is called as a
background process.  Once all pod logs/support bundles have
been collected then they are combined into a single tar file.

Signed-off-by: Walter Lopatka <[email protected]>
Signed-off-by: Walter Lopatka <[email protected]>
Signed-off-by: Walter Lopatka <[email protected]>
@cla-bot cla-bot bot added the cla-signed label Jun 24, 2022
@walterlopatka walterlopatka marked this pull request as ready for review June 24, 2022 23:34
@walterlopatka walterlopatka requested a review from a team as a code owner June 24, 2022 23:34
Copy link
Contributor

@osowski osowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@osowski osowski merged commit d680cda into main Jun 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants