-
Story
-
Resolution: Won't Do
-
Medium
-
Frankfurt Release
-
None
-
Dublin-1 (12/03-01/23), OOM-El Alto Sprint 1
Prior to releasing the Helm Charts over to the project owners, it would be good to have a verification mechanism that ensures changes to a Helm Chart meet some level of standardization. This could be in the form of a schema, linting rules or built-in chart tests.
References of interest.
https://github.com/helm/helm/blob/master/docs/chart_tests.md
https://github.com/helm/chart-testing
The deliverable for this story is a recommendation and implementation of a verification mechanism (that may be extended over time) to enforce standardization rules for ONAP Helm Charts.
Some example rules would be:
- chart must have the certain global values defined in values.yaml
- chart must have the following values in values.yaml:
repository: nexus3.onap.org:10001
image: onap/dmaap/dmaap-mr:1.1.7
pullPolicy: Always
- blocks
-
DMAAP-1267 [DMAAP] Update OOM charts to use new templates before migration
- Closed
-
OOM-1242 Transfer helm chart ownership to remaining teams
- Closed
-
OOM-1817 Use of global.repository inconsistent across Helm Charts
- Closed
- is blocked by
-
OOM-2001 Creation of generic schema and its validation script
- Closed
-
OOM-2002 Integrate schema validation into make process
- Closed
- relates to
-
OOM-1936 Helm Chart Generation
- Closed
-
OOM-2024 Validate generated helm charts against values.yaml schema
- Closed