Configuration model
How CloudEvents connector configuration works in KubeMQ — the enabled-by-default model and the CONNECTORSCE_ENABLE env-var derivation rule.
The CloudEvents connector is configured through the Connectors.CE section of the
KubeMQ server config. It is enabled by default and ships with sensible
production defaults, so most deployments only override a value when they need a
larger SSE buffer or a hard cap on concurrent subscriptions. This page explains the
enable model and how config keys map to environment variable names — for the full
field list, validation rules, and TOML/Env/Docker examples, see the
full field reference.
Enabled by default
The CloudEvents connector is on as soon as kubemq-server starts — the /ce/*
routes on the shared HTTP server are live
with no flag to set. You never enable it with =true; you only set its enable
variable to false to turn it off.
docker run -d -p 8080:8080 -p 9090:9090 -p 50000:50000 -e KUBEMQ_TOKEN=YOUR_LICENSE_KEY -e CONNECTORSCE_ENABLE=false europe-docker.pkg.dev/kubemq/images/kubemq:nextThe enable variable is CONNECTORSCE_ENABLE — with no underscore between
CONNECTORS and CE. Older KubeMQ docs and the configuration reference list
CONNECTORS_CE_ENABLE (with an underscore), which does not bind to the
Connectors.CE.Enable field and is silently ignored. The correct name is derived
from the server's env-var transform — see
Environment variable names below and the
shared HTTP server enable model.
Environment variable names
KubeMQ derives each environment variable from its dotted config key by inserting
underscores at word boundaries, dropping the dots, and upper-casing. Acronyms with
no lowercase boundary (like CE) stay joined to the preceding segment — which is
why the enable variable is CONNECTORSCE_ENABLE and not
CONNECTORS_CE_ENABLE.
The full config key to environment variable mapping table is in the configuration reference.
The CloudEvents connector shares the HTTP server's port (9090), body limit, CORS,
and TLS settings. Those are configured under Connectors.Http and documented once
in Shared HTTP server — not repeated here.
Was this page helpful?