Installation automation and customization (Helm)

[thschue]

To simplify automated installation and customization, a Helm Chart for the lifecycle toolkit should be created and pushed to a Helm registry. Furthermore, we should add the necessary automation to push the information to artifact hub. The generation of the Helm chart could be similar to this: open-feature/open-feature-operator#137

Requirements:

• Publicity over Artifacthub
• Simplify installation via Helm

Definition of done:

• Helm Chart is created
• Helm Chart is pushed to the registry and updated with each release
• The chart is tested
• Helm Chart is visible on Artifact Hub
• Documentation as in place and getting started guide adapted

Stories

Beta Give feedback

1. Research: Automation of Helm Chart releases and maintenance #426
   +0
   
2. Research: CRD to configure KLT #545
   +0
   
3. Set up Options/Config CRD for KLT with OTel collector URL #593
   +0
   
4. Set up helm chart through kustomize overlay #600
   +0
   
5. Set up automation to push generated helm chart to chart repo #594
   +0
   
6. Helm chart repo setup with automatic chart releases, values docs generation #595
   +0
   
7. Set up artifact hub annotations #596
   +0
   
8. Adapt docs to use helm chart instead of manifests #597
   +0
   
9. Test KLT helm chart with schedule #598
   +0
   
10. Operator :: Accept LogLevel #724
    good first issue +1
    
11. Investigate CRDs behavior's during upgrade #784
    +0
    
12. Helm chart: configuration of basic resources #840
    enhancement +1
    

[thisthat]

An important configuration for Helm is the OTel collector URL and port

[mowies]

New open questions:

• How can we realize feature flags with helm values where we want to enable/disable whole k8s resources that are intially managed by kustomize?

[thisthat]

Another example of project using Kube builder & helm: https://github.com/jthomperoo/predictive-horizontal-pod-autoscaler

[mowies]

This epic is fully implemented and will be released with the next version of KLT