projectriff / http-gateway Goto Github PK

The gateway reading state from the API Server is a mixing of the control plane and data plan that should be avoided.

Instead, we could have the controller write a riff-streams ConfigMap that includes that names and addresses of each stream. Then the gateway could mount the ConfigMap and read the configuration off disk. This would mean that the http-gateway would be scoped to a namespace, but that's probably good thing anyway.

Other protocol gateways could use the same ConfigMap down the road.

This will provide a way to embed that library in components that need to connect to liiklus (our "streaming gateway") in a way that is compatible with the opinionated way riff has to serialize data.
The code is already there, so all that is needed is to chose a name (which will be part of the go module "identity"). Some candidates are

• projectriff/stream-go-client
• projectriff/streaming-gateway-go-client
• projectriff-gateway/go-client

Dependabot couldn't parse the go.mod found at /go.mod.

The error Dependabot encountered was:

go: k8s.io/[email protected]: invalid pseudo-version: does not match short name of revision (c18f71bf2947)