Changelog

1.2.0

Breaking changes

• Expose full router container configuration via routerContainer spec

  The Supergraph and SupergraphSet CRDs now expose a routerContainer field under spec.podTemplate for fine-grained control over the router container, including lifecycle hooks, liveness/readiness/startup probes, additional ports, and volume mounts. spec.podTemplate.additionalVolumes is also now available for mounting volumes into containers in the router pods. As a result, the Supergraph and SupergraphSet CRDs have been bumped from v1alpha2 to v1alpha3.

  Several fields have moved from spec.podTemplate into the new spec.podTemplate.routerContainer sub-object. Existing Supergraph and SupergraphSet resources using these fields must be updated:

  Old field	New field
  spec.podTemplate.env	spec.podTemplate.routerContainer.additionalEnv
  spec.podTemplate.envFrom	spec.podTemplate.routerContainer.additionalEnvFrom
  spec.podTemplate.resources	spec.podTemplate.routerContainer.resources
  spec.podTemplate.securityContext	spec.podTemplate.routerContainer.securityContext

  See our documentation for more details as to exact fields exposed

Features

• Add installCRDs and rbac.create flags to Helm chart values

  Set these to false when installing a second instance of the operator in the same cluster. installCRDs: false skips CRD creation so Helm does not conflict with the CRDs owned by the first installation, and rbac.create: false skips ClusterRole creation so the existing ClusterRoles are reused with new namespace-scoped RoleBindings.

Bug fixes

• Bump dependencies to resolve GHSA-65p9-r9h6-22vj, GHSA-vw5v-4f2q-w9xf, and GHSA-hfpc-8r3f-gw53.

• Improve Argo Rollouts detection and compatibility with namespaced mode

  Argo Rollouts availability detection and the Rollout resource watcher have been updated to work correctly when the operator is running in namespaced mode alongside a namespace-scoped Argo Rollouts install.

1.1.1

Bug fixes

• Fix 404 errors when Argo Rollouts is not installed