Integrate the kgateway chart into the repository

[timflannagan]

Is your feature request related to a problem? Please describe.

We need a way for users to install the kubegateway project going forward. Historically, using helm has been the go-to option for most of the OSS Gloo users and we need to continue supporting that.

Describe the solution you'd like

Design a new helm chart from scratch. If needed, determine any migration gaps for existing GW API users.

DoD:

• Any image component needed to pass the conformance suite
• Functional helm chart can be deployed and passing CI checks
• Defaults to the ghcr.io registry
• Published helm chart artifacts via release.yaml workflow
• CI is passing all checks

Out-of-scope:

• Removing legacy chart. That can be done as a follow-up.

Describe alternatives you've considered

Avoid initial helm chart support. Users can install the kubegateway project via other options or tooling (e.g. kubectl apply static manifest, kustomize, etc.).

Additional Context

This is the tracker for the helm chart work that's outlined in the high-level #10363 epic.

[lgadban]

This should also handle the publishing of the binary?

Related: what do we do w.r.t. envoy, see: https://github.com/orgs/k8sgateway/projects/3/views/6?pane=issue&itemId=93313462

[timflannagan]

@lgadban s/binary/chart here right? I think that's fine to add to the scope of this issue. We can always split into separate issues if there's some open questions w.r.t where to publish the chart. I'll add a tasklist to this issue later today.

[lgadban]

No I mean the binary/image of the controller that will be referenced within this helm chart.
IIUC as of now we do not publish that either

[timflannagan]

WDYT about creating a tracker for all the release-related work then? Does the cloudbuilder bits release the binary as well? I think we could leverage goreleaser to build and publish the binary & image or massage everything together in GHAs.

[timflannagan]

Just talking aloud, I think publishing the binary & image is more important than the helm chart work right now. Users can install the required CRDs & other misc. k8s resources using a static manifest.

[lgadban]

I think that's fine, I had assumed this was intended to be the larger tracker that covered:

• https://github.com/orgs/k8sgateway/projects/3/views/6?pane=issue&itemId=91127810
• https://github.com/orgs/k8sgateway/projects/3/views/6?pane=issue&itemId=91128540

And initially https://github.com/orgs/k8sgateway/projects/3/views/6?pane=issue&itemId=91129014 but per slack discussion we will treat as a separate issue

[timflannagan]

@lgadban Created #10441 to house the release-related work items you were mentioning. Updated this issue to be a sub-task under that new umbrella issue.

[timflannagan]

TODO: Follow-ups to the #10485 which integrated the new chart with CI. Either track those items here or close this out and track in the epic.

[timflannagan]

Closing - all the line items are now done. Additionally, the #10545 has merged which removed the legacy gloo chart.