mdebarros opened a new issue, #5740:
URL: https://github.com/apache/camel-k/issues/5740

   ### Requirement
   
   As a [Tester] I want to have [packaged Helm Charts as part of 
daily-snapshot-releases, pre-releases and final-releases] so that [I can 
properly test a release]
   
   ### Problem
   
   Helm charts are only published on final releases.
   
   To be able to test daily-snapshot-releases, and pre-releases using Helm 
installations - one must manually pull the associated "tag" from Github and 
build the Helm chart, and override the image on the Helm `values.yaml`. When 
testing with this approach using IaC, it is necessary to manually publish the 
Helm chart to an intermediate Helm repo. 
   
   This should instead be made available as part of the release process, 
similar to a Docker Image.
   
   ### Proposal
   
   # Summary
   
   Publish a Helm chart whenever a Docker Image is published.
   
   # Suggested approach:
   
   1. As part of all daily-snapshot-releases, pre-releases and final-releases, 
Helm charts should be published to the applicable Helm repository (i.e. 
https://apache.github.io/camel-k/charts) whenever a Docker image is published 
to either official or test Docker repositories (i.e. 
https://hub.docker.com/r/camelk/camel-k/tags or 
https://hub.docker.com/r/testcamelk/camel-k/tags). 
   
   2. All Github releases (inc daily-snapshots, pre, and final releases) should 
include the packaged Helm chart as part of the attached artefacts.
   
   3. Candidate releases are currently released as a tag on Github, but I 
propose that they should similarly be created as a Github release marked as a 
`pre-release`. Upon official release this should instead be removed, and marked 
as `latest`.
   
   ### Open questions
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to