webhookrelay-operator icon indicating copy to clipboard operation
webhookrelay-operator copied to clipboard

A lightweight tunnelling operator to receive & process webhooks/API requests without public IP or load balancers in your Kubernetes cluster

Results 6 webhookrelay-operator issues
Sort by recently updated
recently updated
newest added
trafficstars

Is using this article to configure Webhook relay for my atlantis lab on kubernetes. I did folow all intructions but when I configured `WebhookRelayForward`, I received the follwoing error: ```json...

The k8s deployment created by the operator defaults to an image - presuming it's amd64 - which throws an exec format error on startup. As far as I can see,...

Support the `WEBSOCKET_TRANSPORT=true` environment variable, documented here https://docs.webhookrelay.com/installation-options/containerized/docker This is to cover use cases where tcp/8080 (default GRPC port) is not allowed out of the client network This lack of...

When we create a bucket via the operator, there isn't a way to lock the destination path. For a lot of our workloads the path we are outputting to matters...

enhancement

Currently the Operator can reference secrets in other namespaces via secretRef, which may enable namespace-scoped users to access secrets in their unauthorized namespaces. Perhaps it's better to limit reference in...