CORTX-34359: Added Helm chart and its prerequisites

[Sanket292001]

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

Problem Statement

• Added Helm chart for dashboard and elasticsearch application deployment

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

[Sanket292001]

Codacy issues:

File: solutions/dashboard/charts/prerequisites/local_path_provisioner.yaml

Issues:

• Minimize the admission of containers with the NET_RAW capability
• Minimize the admission of containers with capabilities assigned
• Image Pull Policy should be Always
• Use read-only filesystem for containers where possible
• Minimize the admission of root containers
• Memory requests should be set
• Readiness Probe Should be Configured
• Containers should not run with allowPrivilegeEscalation
• CPU requests should be set
• Apply security context to your pods and containers
• Liveness Probe Should be Configured