Skip to content

Istio configuration after the bb-common migration

The Mattermost Operator chart no longer supports the package-level istio.hardened API. Moving that map under bb-common does not make it valid.

Use the bb-common migration guide and the supported settings in chart/values.yaml. The shared Big Bang bb-common guide describes mesh, route, and policy configuration.

For a sidecar deployment, the following umbrella override enables the mesh integration, restricts outbound traffic to registered services, and generates authorization policies from the package’s network policies:

packages:
  mattermostOperator:
    values:
      bb-common:
        istio:
          enabled: true
          sidecar:
            enabled: true
            outboundTrafficPolicyMode: REGISTRY_ONLY
          authorizationPolicies:
            enabled: true
            generateFromNetpol: true

For direct Helm installations, use the bb-common block without the packages.mattermostOperator.values nesting. The umbrella owns namespace injection and global mesh mode; these package settings do not enable namespace injection by themselves. Use the umbrella’s ambient configuration for an ambient deployment rather than enabling a sidecar resource.

Replace custom ServiceEntry and AuthorizationPolicy overrides with bb-common.istio.serviceEntries.custom and bb-common.istio.authorizationPolicies.custom, respectively. Inspect the rendered resources and verify API-server connectivity and operator reconciliation after changing network restrictions.