helm: provisioning "gateway" support for nginx-gateway-fabric helm chart

[arukiidou]

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

Currently, NGF does not seems to be provisioning Gateway

What would you like to be added: provisioning "Gateway" resource.

Why this is needed:

After deploying the NGF, the cluster administrator must also deploy the gateway. NGF and Gateway cannot be used at the same time, making Gitops more difficult This is not sufficient given the gateway-api persona.

Additional context some charts support Gateway

example: traefik chart supports this.

[mpstefan]

Talked about this issue in our community meeting. We think this makes sense, especially from the operator persona.

Looking at the Traefik example, we fairly sure we want something less opinionated in terms of how many ports, certificates, etc and should be able to provide a more flexible experience. But there has to be some limit...

What level of customization are you looking for in the Gateway resource? When looking at the API specification, what level of customization would you expect for each type?

Also, how are you planning on managing TLS certificates with respect to the Gateway?

[arukiidou]

@mpstefan

For me, I generally hope to be able to reproduce the following. In addition, annotations (required if using cert-manager)

Also, how are you planning on managing TLS certificates with respect to the Gateway?

For now, manual certificate management yet 😑.

[mpstefan]

Thanks @arukiidou, we'll be discussing this item at our next community meeting on Monday.

[pleshakov]

We discussed in our community meeting today.

We think it will be useful.

We're thinking about allowing cluster operators to fully customize annotations of the Gateway as well as Listeners. Do you think it will address your use case?

[arukiidou]

Thank you! Perhaps it will fit my use case

[mpstefan]

Moved to 2.0 to be done as a part of the data and control plane separation since the implementation will change.