Support provisioning of Gateway(s) in helm chart

[bjee19]

Proposed changes

Support provisioning of Gateway(s) in helm chart.

Problem: Users would like to provision a Gateway through the helm chart.

Solution: Support provisioning of Gateway(s) in helm chart.

Testing: Manually tested templating and installation of an example values.yaml file.

Closes #1533

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

Support provisioning Gateway resources through helm chart. 

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.77%. Comparing base (807ff92) to head (6ce4773).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3399      +/-   ##
==========================================
+ Coverage   86.74%   86.77%   +0.02%     
==========================================
  Files         129      129              
  Lines       14928    14928              
  Branches       62       62              
==========================================
+ Hits        12950    12954       +4     
+ Misses       1827     1823       -4     
  Partials      151      151              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bjee19]

With this example values.yaml file:

gateways:
  - name: "nginx-gateway"
    namespace: "default"
    labels:
      "key": "value"
      "keytwo": "valuetwo"
    annotations:
      "keyannotations": "valueannotations"
    spec:
      gatewayClassName: "nginx"
      infrastructure:
        annotations:
          service.annotations.networking.gke.io/load-balancer-type: Internal
      listeners:
        - name: "http"
          port: 80
          protocol: "HTTP"
        - name: "https"
          port: 443
          protocol: "HTTPS"
          tls:
            mode: Terminate
            certificateRefs:
              - kind: Secret
                name: cafe-secret
                namespace: certificate
          allowedRoutes:
            namespaces:
              from: Same
  - name: "nginx-gateway2"
    spec:
      gatewayClassName: "nginx"
      listeners:
        - name: "http1"
          port: 801
          protocol: "HTTP"

I get the following Gateway resources when printed out through helm template:

---
# Source: nginx-gateway-fabric/templates/gateway.yaml
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: nginx-gateway
  namespace: default
  labels:
    key: value
    keytwo: valuetwo
  annotations:
    keyannotations: valueannotations
spec:
  gatewayClassName: nginx
  infrastructure:
    annotations:
      service.annotations.networking.gke.io/load-balancer-type: Internal
  listeners:
    - name: http
      port: 80
      protocol: HTTP
    - name: https
      port: 443
      protocol: HTTPS
      allowedRoutes:
        namespaces:
          from: Same
      tls:
        certificateRefs:
        - kind: Secret
          name: cafe-secret
          namespace: certificate
        mode: Terminate
---
# Source: nginx-gateway-fabric/templates/gateway.yaml
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: nginx-gateway2
spec:
  gatewayClassName: nginx
  listeners:
    - name: http1
      port: 801
      protocol: HTTP
---

Also confirmed no gateways included in values.yaml, correctly does not produce a gateway object when deploying through helm.

[sjberman]

Nice work!

[salonichf5]

nice work !