Spike to determine what package tests still need to be enhanced

From Epic:

Enhance Application Tests This phase fill out more robust functional testing for each of the following components:   This could be completed with cypress or API tests.   Ideally the use of Helm Chart tests infrastructure can be added to each package to implement the test execution and the CI pipeline for bigbang extended to support execution of helm chart tests at merges.

Logging

• Verify that Kibana is actively indexing logging information from components.

or

• Issue opened

Cluster Auditor

• Verify that the violations index is present and contains information

or

• Issue opened

Monitoring

• Verify that the Kubernetes Dashboards and metrics are present
• Verify that the istio dashboards are present

or

• Issue opened

Prometheus

• Verify that all apps are being scraped, no errors

or

• Issue opened

GitLab & Runners

• Create new public group with release name. Example release-1-8-0
• Create new public project with release name. Example release-1-8-0

or

• Issue opened

Anchore

• Verify that this application can scan an image

or

• Issue opened

Argocd

• login with admin password
• Create application

*click* create application
application name: argocd-test
Project: default
Sync Policy: Automatic
Sync Policy: check both boxes
Sync Options: check both boxes
Repository URL: https://github.com/argoproj/argocd-example-apps
Revision: HEAD
Path: helm-guestbook
Cluster URL: https://kubernetes.default.svc
Namespace: argocd-test
*click* Create (top of page)

Delete application

or

• Issue opened

Minio (Note that a helm chart test exists for this work)

• Create bucket
• Store file to bucket
• Download file from bucket
• Delete bucket and files

or

• Issue opened

Mattermost

• Need to define a good test here

or

• Issue opened

Velero

• Backup PVCs and verify that a Restoration can be performed

or

• Issue opened

AC:

• - Issues open for packages that still need enhancement to their helm tests.