-
Story
-
Resolution: Won't Do
-
High
-
Frankfurt Release
-
None
-
OOM-El Alto Sprint 1
As the number and complexity of Helm Charts grows, it is becoming harder to maintain standardization across them all. Standardization is important as it allows for consistent behaviors across all ONAP applications. This includes the ability for all applications to reference the same global configuration values for docker repository, enabling debugging and using a default storage class provisioner. Even more importantly, provide consistent upgrade and rollback mechanisms.
To address this complexity, the A&AI team has demonstrated an approach that allows for further templating of common standardized portions of a Helm Chart. This allows for a central location in which to change and evolve common Helm Chart logic. Now using these common .tpls, it is possible to generate the Helm Chart for every ONAP application. It also makes it much easier to onboard new applications as this generation approach is mostly data driven from a provided values.yaml file.
- blocks
-
OOM-1249 Transfer DMaaP artifacts
- Closed
-
OOM-1256 Transfer POLICY artifacts
- Closed
-
OOM-1257 Transfer PORTAL artifacts
- Closed
-
OOM-1258 Transfer SDC artifacts
- Closed
-
OOM-1259 Transfer SDNC artifacts
- Closed
-
OOM-1260 Transfer SO artifacts
- Closed
-
OOM-1817 Use of global.repository inconsistent across Helm Charts
- Closed
-
OOM-2168 Transfer CDS artifacts
- Closed
- relates to
-
OOM-1505 Implement Standardized Helm Chart verification
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
1.
|
Create Common Templates for Kubernetes Objects | Closed | vk250x | |
2.
|
Convert all the AAI sub charts to use common template | Closed | vk250x | |
3.
|
Create documentation for the common templates | Closed | vk250x | |
4.
|
Extract aai components into components dir | Closed | vk250x | |
5.
|
Add components folder to dmaap helmignore | Closed | vk250x | |
6.
|
Update the onap-starter to use common templates | Closed | vk250x | |
7.
|
Support for updating helm chart versions in requirements.yaml | Closed | Unassigned | |
8.
|
Validate generated helm charts against values.yaml schema | Closed | vk250x |