Seagate / cortx-re

CORTX Release Engineering Scripts and Dockerfiles.

https://github.com/Seagate/cortx

GNU Affero General Public License v3.0

5 stars 52 forks source link

CORTX-34324: Add new code for dashboard #1239

Closed Sanket292001 closed 2 years ago

Sanket292001 commented 2 years ago

Problem Statement

Creating a dashboard to verify the status of different tools like Port Scanner and Codacy. There will be one Main Dashboard showing the status of multiple tools.

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

View rendered solutions/community-deploy/CORTX-Deployment.md View rendered solutions/dashboard/ElasticsearchKibanaInstallation.md View rendered solutions/dashboard/README.md

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

cla-bot[bot] commented 2 years ago

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.

Sanket292001 commented 2 years ago

Most of the CODACY issues are resolved. Some remaining issues in YAML are:

Prefer using secrets as files over secrets as environment variables
Minimize the admission of root containers
Liveness Probe Should be Configured
Readiness Probe Should be Configured
Use read-only filesystem for containers where possible

YAML Files:

solutions/dashboard/config/codacy/CodacyDeployment.yaml
solutions/dashboard/config/logstash/LogstashDeployment.yaml
solutions/dashboard/config/portscanner/PortScannerDeployment.yaml