Problem: When provisioning the NGINX LoadBalancer Service, the IPFamily that's set in the NginxProxy resource (default dual) was not honored.

Solution: By default, set the IPFamily to PreferDualStack. If a user has specified otherwise in the NginxProxy resource, then set to SingleStack. The IPFamilies list is populated automatically by k8s based on the policy.

…3491)

Update module github.com/nginx/agent/v3 to v3.0.1 (#3489)

* Update module github.com/nginx/agent/v3 to v3.0.1

| datasource | package                   | from   | to     |
| ---------- | ------------------------- | ------ | ------ |
| go         | github.com/nginx/agent/v3 | v3.0.0 | v3.0.1 |




* Update dockerfiles

---------

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Saylor Berman <[email protected]>

Add agent version to CHANGELOG template (#3467)

Co-authored-by: Saylor Berman <[email protected]>

Feat: Add helm values for cert-generator Job pod placement (#3493)

Problem: Deploying the new version 2.0.0 chart we see the Job/foo-cert-generator pod stuck on pending scheduling when all cluster nodes have taints.

Solution: Add the ability to inject job.spec.template.spec.{affinity,nodeSelector,tolerations,topologySpreadConstraints} to alter pod placement. If you prefer to only add a subset of these, like only tolerations was needed in my case, please do inform and I can adjust.

Co-authored-by: Bogdan-Adrian Burciu <[email protected]>

#3500)

gives enough time for argocd to verify job has finished (#3487)

Problem: Argocd can never find the job completion as TTL is set to 0

Solution: Sets the default ttl seconds to 30 so that argocd has enough time to verify.

Co-authored-by: ab-andresc <[email protected]>

…ice labels #3499 (#3501)

Feat: Add user-provided helm values for additional control plane service labels (#3499)

Problem: As a user that uses prometheus for everything metrics, I would like to target the control plane service with a specific label.

Solution: Add the ability for users to provide additional service labels for the NGINX Gateway Fabric control plane service in the helm chart.

Testing: Used helm lint/install --dry-run to make sure the k8s resources are created correctly

Co-authored-by: Michael Kranz <[email protected]>