The rendered GatewayClass carried a `metadata.namespace` set to the
release namespace. GatewayClass is cluster-scoped, so the field has no
meaning there.

Installing through the Helm CLI was unaffected but other clients may
fail handling this manifest. This was reported with the GitLab Operator.

Relates https://gitlab.com/gitlab-com/request-for-help/-/work_items/5148

Changelog: fixed

Backport 10.2: Remove namespace from GatewayClass

See merge request !5229

Merged-by: João Alexandre Cunha <j.a.cunha@gmail.com>
Approved-by: Stefan Bordei <sbordei@gitlab.com>
Approved-by: João Alexandre Cunha <j.a.cunha@gmail.com>
Co-authored-by: Clemens Beck <cbeck@gitlab.com>

feat(gitlab-shell): add BackendTrafficPolicy for PROXY v2 with Envoy Gateway

Closes #6588

Changelog: fixed

See merge request !5207

Merged-by: Jason Plum <jplum@gitlab.com>
Reviewed-by: João Alexandre Cunha <j.a.cunha@gmail.com>
Reviewed-by: Nailia Iskhakova <niskhakova@gitlab.com>
Co-authored-by: Nailia Iskhakova <niskhakova@gitlab.com>
Co-authored-by: Duo Developer <service_account_group_9970_1976e9ecde3c53c783b64edb9ae993eb@noreply.gitlab.com>

(cherry picked from commit 55f3b03c)

522e64f6 feat(gitlab-shell): add BackendTrafficPolicy for PROXY v2 with Envoy Gateway
4001ff48 style: indent nested if blocks in backendtrafficpolicy.yaml
f482c633 fix(gitlab-shell): gate BackendTrafficPolicy on outbound PROXY predicate
25bd6583 Trim down comments per review
fb2e200a Add docs entry fr proxy forwarding to external envoy
5d0ac228 Guard BackendTrafficPolicy on proxyProtocol true

Co-authored-by: Jason Plum <jplum@gitlab.com>

The bundled Prometheus subchart (29.17.0) renders scrape configs from two
additive sources: its own populated `scrapeConfigs` map (~10 default jobs)
and GitLab's legacy `serverFiles."prometheus.yml".scrape_configs`. GitLab
attempted to suppress the upstream defaults with `scrapeConfigs: null`, but
`null` is silently dropped when coalescing into the condition-gated
(`prometheus.install`) subchart (helm/helm#31446, helm/helm#9136), so the
upstream defaults survived and collided with GitLab's own jobs, causing
Prometheus to fail to load with `found multiple scrape configs with job
name "prometheus"`.

Replace the ineffective null with an empty list, `scrapeConfigs: []`. A
non-null value propagates through the condition-gated coalesce, and a
list-typed value replaces the upstream default map wholesale (list-vs-map
type mismatch), leaving only GitLab's own serverFiles jobs. Rendering now
emits exactly the 5 GitLab jobs, each once, with no duplicates, no
placeholder job, and no Helm coalesce warning.

Interim fix; it relies on Helm's list-replaces-map coalesce behavior. The
durable fix (migrating GitLab's jobs onto the upstream `scrapeConfigs`
structure) is tracked in #6413.

Changelog: fixed

Backport 10.2: replace default scrapeConfigs to fix duplicate scrape job

See merge request !5240

Merged-by: Clemens Beck <cbeck@gitlab.com>
Approved-by: Clemens Beck <cbeck@gitlab.com>
Co-authored-by: Lucas Li <lli@gitlab.com>

Backport 'duo/feature/6588-shell-backendtrafficpolicy-proxy-protocol' into '10-2-stable'

See merge request !5244

Merged-by: Nailia Iskhakova <niskhakova@gitlab.com>
Approved-by: Nailia Iskhakova <niskhakova@gitlab.com>
Co-authored-by: João Alexandre Cunha <j.a.cunha@gmail.com>

[ci skip]

[ci skip]