Release 1.6.0

Checklist for things to validate for release 1.5.0

TODO:

• Create release branch
• release specific code changes with a single MR/commit
  • Bump self-reference version in base/gitrepository.yaml
  • update chart release version char/Chart.yaml
  • update /Packages.md with any new Packages
  • update CHANGELOG.md with links to MRs and any upgrade notices/known issues
• Deploy release branch on Dogfood cluster
• Build draft release notes
• Update README.md using helm-docs
  • docker run -v "$(pwd):/helm-docs" -u $(id -u) jnorwood/helm-docs:v1.5.0 -s file -t .gitlab-ci/README.md.gotmpl --dry-run > README.md
• After validating release candidate create official release tag
• Cherry-pick release commit(s) as needed with merge request back to master branch

https://repo1.dso.mil/platform-one/big-bang/customers/bigbang

TESTING:

• Stand up RKE cluster
• Deploy all the apps with SSO
• Apps stand up and are healthy
  • Virtual Services and cert are correct
  • image pull secret
• Confirm SSO works correctly
• Logging
  • Get logs from all apps.
• Cluster Auditor
  • violations index is present and contains images that aren't from registry1
• Monitoring
  • Contains Kubernetes Dashboards and metrics
  • contains instio dashboards (no data coming in #65 (closed) )
• Kiali shows no errors
• Sonarqube - Deploys, can get tokens
• GitLab + Runners
  • git clone and git push repos
  • docker push and docker pull image to registry
  • Change icon is user settings
  • Test simple CI pipeline
• Anchore
  • One-Time Scan against image from registry.bigbang.dev or registry1.
• Argocd
  • Create application
  • connect to our Gitlab
• Minio deploys.
• Test Mattermost
• Test Velero
  • Backup PVCs
  • Restore PVCs

Candidate Release Notes