Automating updates to valkey-helm

[hieu2102]

We can create a GitHub action to automate changes to Helm's templates (e.g., automating #192)

Something similar is done for valkey-doc: https://github.com/valkey-io/valkey-release-automation/blob/main/.github/workflows/update-valkey-doc.yml

[bjosv]

cc @SuperQ

[jdheyburn]

Perhaps it would be good to list out what updates we would automate. I see that there is a draft PR raised for ClusterRole in #200.

valkey-operator -> valkey-helm
config/crd/bases/valkey.io_valkeyclusters.yaml -> crds/valkey.io_valkeyclusters.yaml
config/crd/bases/valkey.io_valkeynodes.yaml -> crds/valkey.io_valkeynodes.yaml
config/rbac/role.yaml -> templates/clusterrole.yaml
config/rbac/leader_election_role.yaml -> templates/leader-election-role.yaml

# to add
config/rbac/metrics_reader_role.yaml -> templates/metrics-reader-role.yaml
config/rbac/metrics_auth_role.yaml -> templates/metrics_auth_role.yaml
config/rbac/metrics_auth_role_binding.yaml -> templates/metrics_auth_role_binding.yaml

I couldn't find it, but I'm sure someone has previously mentioned of a tool that automates a sync similar to this already.

[hieu2102]

I found helmify which automates quite a lot, but the format don't really match with what we already have

[jdheyburn]

Okay, I don't have much of an opinion since we're this early on. I'm fine with not using helmify.

[hieu2102]

kube-prometheus-stack automates synching CRDs

For generating the template files, they use python scripts for that: script, output

I think this is applicable to us too

[hieu2102]

Still looking for an easy way to do it, there don't seem to be many projects out there that offer helm template syncing automation.

Perhaps we can do something simple like CI pipeline checking if there are any files in config/ that are changed by a PR, and remind/check if a PR is created for valkey-helm

[Preisschild]

I already recommended this once in a discussion, but using the kubebuilder helm-v2-alpha plugin would allow automatically creating the helm chart just like the kustomize config/ files and might be worth taking a look at to solve this issue. The oci of the chart would then be published in this repo.