at this moment the new version should appear in the registry:
$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
$ helm search repo bitnami/kafka
NAME CHART VERSION APP VERSION DESCRIPTION
bitnami/kafka 7.3.1 2.4.0 Apache Kafka is a distributed streaming platform.
About the process, there are two paths to update charts:
- Automated changes updating Docker images, dependencies, etc, like this one.
- Contributions from users, like this one.
In both cases, changes should pass through our automated pipeline to be tested before pushing the new version to the Helm registry:
- In the first case, the commit in GitHub appears just a couple of minutes before the chart is pushed to the registry because the changes itself are created by the automated pipeline.
- In the second case, PRs from users should trigger some jobs in our pipeline and execute our tests battery before pushing the chart to the registry, if everything works fine the new chart should appear in the registry in a few hours but if some tests fail, we need to fix them to ensure the chart in registry works properly. In the worst case, this process shouldn't take more than a couple of business days
Carlos R. Hernández