CORTX-34324: Modified port scanner to separate the actual and scan namespace

[Sanket292001]

Signed-off-by: Sanket Salunke sanket.s.salunke@seagate.com

Problem Statement

• Modified port scanner to separate the actual and scan namespace: -> For this modified the CR and CRD and added a new field "scanNamespace". This field stores the namespace to run the service scan. -> The "namespace" field in CR and CRD used as a default port scanner namespace. Example, ConfigMap will use this namespace.
• Modify the port scanner cleanup scripts

Design

• For Bug, Describe the fix here.
• For Feature, Post the link for design

Coding

Checklist for Author

• [x] Coding conventions are followed and code is consistent

Testing

Checklist for Author

• [ ] Unit and System Tests are added
• [ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
• [ ] Testing was performed with RPM
• [ ] Jenkins pipelines used for testing

Impact Analysis

Checklist for Author/Reviewer/GateKeeper

• [ ] Interface change (if any) are documented
• [ ] Side effects on other features (deployment/upgrade)
• [ ] Dependencies on other component(s)

Review Checklist

Checklist for Author

• [x] Jira ID/ COMMUNITY is prefixed in PR title Prefix Syntax - CORTX-<5 digit JIRA ID>: <PR Title> - for Seagate Employees COMMUNITY: <PR Title> - for open source contributors
• [x] PR is self reviewed
• [ ] Jira and state/status is updated and JIRA is updated with PR link
• [ ] Check if the description is clear and explained

Documentation

Checklist for Author

• [ ] Changes done to WIKI / Confluence page / Quick Start Guide

[cla-bot[bot]]

Thanks for your contribution! The CLA bot has flagged your contribution as not having a Contributor License Agreement in place. Note that this is not needed in the overwhelming majority of instances and this warning will usually be ignored. The code reviewers will make a determination and may ask you to sign a CLA or may choose to ignore this warning. More information about this can be found here.