Hi @DanielCastronovo, sorry for the delay; it's been a holiday season. Hope you had a nice Christmas and New Year!

Could you please provide additional points as to why you wish for additional Helm chart? I've been grokking this slightly on my days off and I have some reservations about such a change. So additional clarification on the use cases, pros and cons from your perspective would be helpful.

Hi, sure Helm doesn't support CRDs upgrade, so major helm chart with CRD have 2 helm distinct helm chart :

• for the app
• for CRDs

It's enable to programmatically and not by manual steps to bump a new CRDs.

Pros :

• IAC support
• Gitops
• No more manuels steps
• Reduce the maintenance process
• Specific changelog and release note (give much visibility on BR)

Cons :

• Need 2 charts

Hi @DanielCastronovo, thanks for the write up!

I've been looking around for an alternative solution and it appears that there are hooks that could be utilized to help with upgrades as well. That is, chart hooks pre-upgrade. I didn't try it myself, but it sounds like there can be a Job executed one each upgrade that could update the CRDs. I.e. it should cover most of the points you raised. (except the changelog thing but we also track this in #344) WDYT?

Just to be clear, I'm definitely all for improving the experience with Helm chart; it's just adding a new chart to maintain would take additional time that I need to plan for. And if it's possible to have an alternative solution that won't complicate maintenance of k6-operator too much, that'd be great.

cc @mariuskimmina since you worked on a related PR 🙂