Skip to content

Enable the platform broker and Team Broker by default #1010

Closed

Description

@dimitrieh

Description

The chart defaults forge.broker.enabled and forge.broker.teamBroker.enabled to false, while Docker Compose ships the broker on. A default Kubernetes install therefore has no platform broker.

The broker is the prerequisite for MCP tooling and third-party agent access, which route over MQTT and need no Expert token. It is separately one step of Expert configuration, which additionally needs the Expert token. So on Kubernetes both paths are off until the operator edits values.yaml.

Enable both switches by default, or record here why we cannot and what has to change first.

Acceptance:

  • The original reasons for the off-by-default are written down, with which of them still hold.
  • If enabled: helm install with no extra flags yields a working platform broker plus Team Broker on a cluster meeting the documented prerequisites, and does not hard-fail on one that does not.
  • Kubernetes install docs and the self-hosted enablement guide match the resulting default.

Requested By

https://flowfuse.slack.com/archives/C032Q63FGG1/p1787317316286389?thread_ts=1785850828.729389&cid=C032Q63FGG1

Activity

  1. dimitrieh commented on Aug 21, 2026

    @dimitrieh
    Author
  2. knolleary commented on Aug 21, 2026

    @knolleary
    Member

    To move this forward, it would helpful for us to document:

    • why it is disabled by default (a historic choice that made sense at the time)
    • what currently stops us enabling by default
    • what impact could this have on existing installs

    If there are technical blockers, lets get them written down so we can work out a way forward.

    @hardillb @ppawlowski you both have the context here, so your input is needed.

  3. hardillb commented on Aug 21, 2026

    @hardillb
    Contributor
    • it was disabled because a broker was not needed for core functionality
    • enabled by default means users must have the correct version of the emqx operator installed before installing (it is now listed as a pre-req)
    • customers upgrading will need to ensure all the current pre-reqs are installed before they can upgrade
  4. dimitrieh commented on Aug 21, 2026

    @dimitrieh
    Author

    it was disabled because a broker was not needed for core functionality

    Since the introduction of expert over mqtt and now mcp tooling, this can be considered as needed for core functionality.

    enabled by default means users must have the correct version of the emqx operator installed before installing (it is now listed as a pre-req)
    customers upgrading will need to ensure all the current pre-reqs are installed before they can upgrade

    Can we have gracious errors/fallback in any way, so the configuration can just stand regardless of the emqx operator being installed?

  5. knolleary commented on Aug 21, 2026

    @knolleary
    Member

    it is now listed as a pre-req

    Forgive the basic question, but does that mean:

    1. its documented as a pre-req and relies on the user reading to know what to do
    2. the helm chart checks for and will install it if needed
  6. hardillb commented on Aug 21, 2026

    @hardillb
    Contributor
    1. https://flowfuse.com/docs/install/kubernetes/#prerequisites lists it as a requirement

      EMQX Operator: This installs the operator that deploys the platform's MQTT broker, which is required whenever the broker is enabled.

    2. The helm chart will now object if the operator is not installed
      {{- if eq .Values.forge.broker.enabled true -}}
      {{- if not (.Capabilities.APIVersions.Has "apps.emqx.io/v2beta1") }}
      {{- fail "EMQX Operator not installed. Please install it or disable the broker (forge.broker.enabled=false) before continuing" }}
      {{- end }}

    We may want to update the helm chart to explicitly point to the section of the docs about what version to install

  7. ppawlowski commented on Aug 21, 2026

    @ppawlowski
    Contributor

    I am a little bit lost in the whole conversation - @dimitrieh what kind of problem are we trying to solve here?

  8. dimitrieh commented on Aug 21, 2026

    @dimitrieh
    Author

    @ppawlowski SH users that have never used FlowFuse Expert, should have no friction gates towards using the FlowFuse MCP tooling we release in 3.0. This configuration requirement creates friction, if its not necessary, please remove it.

  9. ppawlowski commented on Aug 21, 2026

    @ppawlowski
    Contributor

    This configuration requirement creates friction

    I do not see a possibility to enable this by default, mainly because:

    • setting ' forge. broker. enabled ' to true requires the EMQX operator to be installed first
    • both forge.assistant.service.token and forge.expert.service.token need to be provided since these are custom values per deployment
  10. ppawlowski commented on Aug 21, 2026

    @ppawlowski
    Contributor

    If we decide to switch the default forge.broker.enabled value to true, this will create friction for everyone who wants to install FlowFuse Platform on a kubernetes cluster.
    Remembering the recent controversies around EMQX, I don't think this is a good idea.

  11. knolleary commented on Aug 21, 2026

    @knolleary
    Member

    @ppawlowski

    Lets separate out the EMQX issue from the technical aspects of the 'enable by default' question

    The helm chart will now object if the operator is not installed

    That should address your first concern right - we can document the requirement and the helm chart will safe guard against it being missing.

    For the tokens - that needs input from other colleagues in terms of how that's intended to work in an 'enabled by default' world.

  12. ppawlowski commented on Aug 21, 2026

    @ppawlowski
    Contributor

    That should address your first concern right - we can document the requirement and the helm chart will safe guard against it being missing.

    As Ben mentioned:

    • in the documentation, in the "Prerequisites" paragraph, point 7, we mention EMQX Operator must be installed
    • with the EMQX operator missing and the forge.broker.enabled value set to true, Helm chart installation will hard fail with the message:
    "EMQX Operator not installed. Please install it or disable the broker (forge.broker.enabled=false) before continuing"
    
  13. dimitrieh commented on Aug 24, 2026

    @dimitrieh
    Author

    For the tokens - that needs input from other colleagues in terms of how that's intended to work in an 'enabled by default' world.

    @Steve-Mcl can you take a look here when you can?

    cc: @knolleary

  14. dimitrieh commented on Aug 24, 2026

    @dimitrieh
    Author

    Pulling the key points out of today's Slack thread (link) so they live here rather than only in Slack.

    Tokens are not part of this ask. forge.assistant.service.token and forge.expert.service.token are only needed for Expert. The MCP tooling and third-party agent access route over the broker and work without them. So "enabled by default" here means the broker switches only, no per-deployment token values.

    The headline is third-party agent access for self-hosted. Assume a self-hosted install that has never set up Expert, so has no tokens. It should still be able to connect an external agent to FlowFuse through the MCP tooling we ship in 3.0, without custom configuration first. The same bridge is needed for Expert too, but Expert then needs the tokens on top.

    The gap is Kubernetes only. Docker ships the broker on and needs no custom config. Kubernetes still does. The ask is to align Kubernetes with the way Docker does it.

    This is not a blocker, it removes a friction point for customers who want to use the new MCP functionality without having set up Expert first. Ideally resolved before Thursday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageNeeds looking at to decide what to do

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions