Vector source through GKE Gateways

[elwinar]

I can't get the vector source to work through the GKE's Gateway.

The aggregator configuration is:

api:
  enabled: true
  address: 0.0.0.0:8686

sources:
  in:
    type: vector
    address: 0.0.0.0:8080
    tls:
      enabled: false

sinks:
  out:
    type: blackhole
    inputs:
    - in

and is exposed via a service and a httproute (the API is enabled for the healthcheck policy).

Trying to send dummy logs to it with the following configuration :

sources:
  in:
    type: "stdin"

sinks:
  out:
    type: vector
    inputs:
      - "in"
    address: https://hostname

results in the following log line:

2025-01-07T08:03:49.027306Z ERROR vector::topology::builder: msg="Healthcheck failed." error=Request failed: status: Unknown, message: "h2 protocol error: http2 error: connection error detected: frame with invalid size", details: [], metadata: MetadataMap { headers: {} } component_kind="sink" component_type="vector" component_id=out

(Relevant logs with debug enabled: vector-log.txt)

I get that I probably misconfigured something, but I can't find it out. I've tried port-forwarding the service locally to rule out missconfiguration of the source/sink and it's working properly, so it's probably the Gateway shitting the bed.

My current gateway is defined as follows:

apiVersion: gateway.networking.k8s.io/v1beta1
kind: Gateway
metadata:
  name: gateway
  namespace: default
  annotations:
    networking.gke.io/certmap: "${certmap}"
spec:
  gatewayClassName: gke-l7-global-external-managed
  listeners:
  - name: https
    protocol: HTTPS
    port: 443

The one listener does TLS termination for me.

I ended up switching to the http_server source to bypass the issue for now, I'll come back to it later. In the meantime, I would welcome any pointer or example if someone got it working.

[jszwedko]

Hi @elwinar ,

To use the vector source / sink (which use HTTP/2) I think you need to set tls.alpn_protocols: ["h2"] in the vector sink. See some similar discussion around AWS ALBs here: #9901 (comment)

[elwinar]

Thanks for the answer, I'll have a look at it.

[elwinar]

Nope, still

2025-01-13T09:06:46.877229Z  WARN sink{component_kind="sink" component_id=out component_type=vector}:request{request_id=1}: vector::sinks::util::retries: Retrying after error. error=Request failed: status: Unknown, message: "h2 protocol error: http2 error: connection error detected: frame with invalid size", details: [], metadata: MetadataMap { headers: {} } internal_log_rate_limit=true

I've found something about specifying protocols for the gateway that I'll try.