Create initial BigBang compatible chart for Neuvector
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/tree/master/docs/developer/package-integration
It might be easier to track/distribute the tasks here if sub issues are created for different checklist items
Definition of Done Checklist
Package:
-
Do you have a 'main' branch that is default and protected? -
Are all other branches merged or deleted? For master and dev branches, tag the branch commit before deleting the branch so we can retrieve it if necessary. Exception: branches labeled release -
Does the repo contain only the following directories: chart, docs, tests? All other directories should be deleted. -
Is there a CODEOWNERS file containing three code owners? -
Is there a CHANGELOG.md file with initial changes? -
Is there a README.md file documenting basic use? -
Is there a CONTRIBUTING.md file outlining how a new person can contribute? -
Is CICD Setup: https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/docs/developer/package-integration/package-integration-testing.md (Issue Created) -
Have you run helm dep up and added all .tgz file dependencies in chart/charts to the repo? -
Have you updated chart/requirements.yaml or chart/Chart.yaml to point to the file://./charts/.tgz dependencies? -
If the chart has a web interface, have you added a VirtualService using hostname that is conditionally added if istio.enabled is true? Verify this works using the web address.(issue created) -
If the chart integrates with Prometheus monitoring, have you added a Service and ServiceMonitor that are conditionally (issue created) added if monitoring.enabled is true? Verify this using Prometheus to check targets. Might want to think more about how to add this chart/components in, rather than having it be a seperate chart: https://github.com/neuvector/neuvector-helm/tree/master/charts/monitor (issue created) -
Does your package have resource requests and limits set and equal to each other? (Issue created) -
Do you have a tag on your main branch for the Big Bang release version of the package? (issue created) -
Have all of your images been updated to pull from registry1.dso.mil. Exception: If there is no Iron Bank image, are you (issue created) pulling from registry.dso.mil? (done/issue created) -
If the package supports SSO, have you integrated SSO settings? (ISSUE OPENED) -
If the package requires a database, have you integrated external database settings? Needs clarification -
If the package requires storage, have you integrated external storage (e.g. MinIO) settings? Needs clarification -
Are all secrets and certificates removed from the repo? All secrets should be references or randomly generated during deployment. -
Supports working with Istio enabled? (issue created) -
mTLS enforced (issue created) -
Insert NetworkPolicies
Testing:
-
Have you verified the CI/CD pipeline passes? -
Add things that should be tested here as part of the deployment
Edited by brandt keller