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 --pull always --platform linux/amd64 --name kubemq --hostname kubemq -p 127.0.0.1:8080:8080 -p 127.0.0.1:9090:9090 -p 127.0.0.1:50000:50000 -e STORE_ENGINE=next -e STORE_NEXT_ACK_POLICY=strict -e STORE_STORE_PATH=/kubemq/store -e API_BIND_ADDRESS=0.0.0.0 -e CONNECTORSCE_ENABLE=false -v kubemq-data:/kubemq/store europe-docker.pkg.dev/kubemq/images/kubemq-next:latestThe primary enable variable is CONNECTORSCE_ENABLE — with no underscore between
CONNECTORS and CE. The underscored CONNECTORS_CE_ENABLE is bound as an alias
to the same Connectors.CE.Enable field, so either form works. CloudEvents is the only
gateway with this alias — MCP and A2A bind the collapsed form only. The primary 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 primary enable variable is CONNECTORSCE_ENABLE. The server also binds the
natural CONNECTORS_CE_* names as aliases for every CloudEvents setting, so both
forms work.
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?