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

V0.13.0 merge #384

Merged
merged 10 commits into from
Sep 15, 2022
Merged

V0.13.0 merge #384

merged 10 commits into from
Sep 15, 2022

Conversation

walterlopatka
Copy link
Contributor

@walterlopatka walterlopatka commented Sep 15, 2022

Description

Merge integration to main.
Also set VERSION to v0.13.0

Breaking change

This includes removing deprecated code see (coming soon) release notes.

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
  • Merge from integration, new release

Applicable issues

N/A

CORTX image version requirements

This change requires the following images:

  • cortx-data:950
  • cortx-rgw:950
  • cortx-control:950

How was this tested?

Standard release qualification:

  • Automated deploy tests
  • logs-status.cloud.sh test
  • Basic S3 IO smoke test
  • Basic upgrade test (950->951)

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 GLOSSARY.md
View rendered charts/cortx/README.md
View rendered charts/cortx/README.md.gotmpl

walterlopatka and others added 10 commits September 1, 2022 11:16
Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
CORTX-34141: Add -d option to get-logs-from-pvc.sh

Add a -d option to allow user to specify a subdirectory of the
PVC to collect logs from.

Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
CORTX-34174: Improve options to logs-cortx-cloud.sh

Improve overall usage of options
Update the --help

Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
…377)

Fix status check for Control, data-only

This fixes a regression that was introduced with multi-pod
cortx-control pods.

Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
Signed-off-by: Rick Osowski <rosowski@gmail.com>

Signed-off-by: Rick Osowski <rosowski@gmail.com>
* Remove deprecated code from deploy-cortx-cloud.sh

Signed-off-by: Keith Pine <keith.pine@seagate.com>

* Remove deprecated code from destroy-cortx-cloud.sh

- Misc script cleanup
- Use selectors for PVC deletion
- Remove need for external YAML parsing scripts (use `yq`)

Signed-off-by: Keith Pine <keith.pine@seagate.com>

* Make destroy script quieter

Signed-off-by: Keith Pine <keith.pine@seagate.com>

* Clean up secrets

- Auto-generated secret is now saved in
  "k8_cortx_cloud/auto-gen-secret-${namespace}"
  instead of a subdirectory.
- Localize temporary secret cleanup to function
- Remove vestiges of cortx-configmap chart dir

Signed-off-by: Keith Pine <keith.pine@seagate.com>

* Remove deprecated cortx-control-loadbal-svc Service

Signed-off-by: Keith Pine <keith.pine@seagate.com>

* Fix comment in secret content field

Signed-off-by: Keith Pine <keith.pine@seagate.com>

* Remove deprecated cortx-io-svc-N Service

Signed-off-by: Keith Pine <keith.pine@seagate.com>

Signed-off-by: Keith Pine <keith.pine@seagate.com>
Co-authored-by: Rick Osowski <rosowski@gmail.com>
Signed-off-by: Keith Pine <keith.pine@seagate.com>
Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>

Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
)

status-cortx-cloud.sh was checking the total count of consul pods
against the sum of expected server pods (max(3, #worker-nodes))
and expected client pods.  However, the expected number is based
on the number of worker nodes not tainted w/ NoSchedule.  This
does not work as expected when a node that is normally a worker
node is tainted with NoSchedule.

To fix I have stopped checking for the expected number of
cortx-consul-client pods.  This is not a useful check anyway.

Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>

Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
Co-authored-by: Rick Osowski <rosowski@gmail.com>
Signed-off-by: Walter Lopatka <walter.lopatka@seagate.com>
@cla-bot cla-bot bot added the cla-signed label Sep 15, 2022
@walterlopatka walterlopatka marked this pull request as ready for review September 15, 2022 19:59
@walterlopatka walterlopatka requested a review from a team as a code owner September 15, 2022 19:59
@walterlopatka walterlopatka merged commit 45a3620 into main Sep 15, 2022
@walterlopatka walterlopatka deleted the v0.13.0_merge branch September 15, 2022 21:16
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.

None yet

3 participants