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

CORTX-30943: Support specified namespace for cortx-client pods #216

Merged

Conversation

walterlopatka
Copy link
Contributor

Description

This change fully supports deploying cortx-client pods into the namespace specified by solution.yaml.

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-29043

CORTX image version requirements

No new CORTX image version requirements with this change (but as before it does need to be version 725 or later to support other recent changes).

How was this tested?

I deployed CORTX with "num_clients = 1" to confirm that it deploys into the specified namespace.

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 addresses a CORTX Jira issue:

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

@walterlopatka walterlopatka requested a review from a team as a code owner April 20, 2022 22:42
@cla-bot cla-bot bot added the cla-signed label Apr 20, 2022
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 ccaab4f into Seagate:integration Apr 21, 2022
@walterlopatka walterlopatka deleted the CORTX-30943_cortx_client_namespace branch April 21, 2022 13:37
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