Migrate `manifests/envoy-gateway-config` into EG's helm values instead of raw Yamls

[mathetake]

Description:

Especially, envoy-gateway-config.yaml is generated by EG's helm chart, so maintaining the raw yaml here as well could be troublesome in some cases. I believe everything in the dir can be migrated into EG's helm value input, especially envoy-gateway-config.yaml can be under

https://github.com/envoyproxy/gateway/blob/4b1827909115e2cb509609f773ed58fbd3f47a5e/charts/gateway-helm/values.tmpl.yaml#L98

For redis, I think it can be moved into examples/toke_ratelimit.yaml

[mathetake]

well RBAC might be tricky. I couldn't find an option to add additional one from a quick look

[saileshd1402]

Hi @mathetake, can I assign this to myself and raise a PR?

[mathetake]

sure

[kfox1111]

This should be in the right ballpark to remove the need for the config.yaml

along with:
helm upgrade --install valkey oci://registry-1.docker.io/bitnamicharts/valkey -n envoy-gateway-system

config:
  envoyGateway:
    extensionApis:
      enableEnvoyPatchPolicy: true
      enableBackend: true
    extensionManager:
      hooks:
        xdsTranslator:
          translation:
            listener:
              includeAll: true
            route:
              includeAll: true
            cluster:
              includeAll: true
            secret:
              includeAll: true
          post:
            - Translation
            - Cluster
            - Route
      service:
        fqdn:
          hostname: ai-gateway-controller.envoy-ai-gateway-system.svc.cluster.local
          port: 1063
    provider:
      kubernetes:
        deploy:
          type: GatewayNamespace
        rateLimitDeployment:
          patch:
            type: StrategicMerge
            value:
              spec:
                template:
                  spec:
                    containers:
                    - imagePullPolicy: IfNotPresent
                      name: envoy-ratelimit
                      image: docker.io/envoyproxy/ratelimit:60d8e81b
                      env:
                      - name: REDIS_AUTH
                        valueFrom:
                          secretKeyRef:
                            name: valkey
                            key: valkey-password
    rateLimit:
      backend:
        type: Redis
        redis:
          url: valkey-primary.envoy-gateway-system.svc.cluster.local:6379

[kfox1111]

Could the rbac bits be added to the ai gateway chart?

[mathetake]

yeah i guess rbac can live there