Publish versioned chart

[cehoffman]

What is missing?

A native helm way of installing the chart without cloning the git repository.

Why do we need it?

To integrate with our deployment pipeline, we have to setup a extra pre process that pulls the git repository to extract the helm chart for use in the remaining parts of our pipeline.

Environment

• Twingate Kubernetes Operator version:

  `0.6.2

Anything else we need to know?:

Publishing this through GitHub packages should be fine, but we haven't use that explicitly. We've used the GitHub pages method of publishing the chart many times though.

[linear]

OSS-25 Publish versioned chart

[ekampf]

Yep. Definately something we need to do but not so simple so might take some time...

[svyatoslavmo]

@ekampf any ETA on this one? It would provide easier deployment path

[ekampf]

@svyatoslavmo no ETA I can share yet but it is at the top of my list

[ekampf]

@svyatoslavmo would love some feedback on #265
Publishing to an OCI repo on github solves answers your needs right?

[svyatoslavmo]

Yes, thank you! @ekampf
I would also suggest to version Helm chart and operator together, as Grafana does.

[ekampf]

@svyatoslavmo isnt the reason Helm chart has version and appVersion as separate properties is to avoid this?
Helm chart rarely changes do we really want to update its version with every release?

[svyatoslavmo]

Yes, because it's one version for all changes. Your end user will bump just the chart version, regardless what's been changed.
check this out

[ekampf]

I see... ok will make it work on #265

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[cehoffman]

I'm ok with either method in general, but for the way my company currently manages these type of resources moving the chart version in lock step with the application version is easiest. Hosting on GitHub OCI is also perfectly fine.

[AlexisDaciuk]

Any updates on this? we are using the Operator in our clusters but it's not great to have to install it by hand

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[AlexisDaciuk]

bump

[ekampf]

@AlexisDaciuk sorry it has been taking so long... PR is almost ready at #479

[HaddadJoe]

Seems like the PR is ready, we would also benefit from that. Any timelines for the deployment?

[ekampf]

@HaddadJoe PR is merged and new operator released 😃