Linkerd

If your application is running using Linkerd, you can set up sandbox routing using Signadot's DevMesh. The DevMesh is a system of envoy-based sidecars that are built into the Signadot Operator and offer lightweight request routing functionality. The DevMesh sidecars are designed such that they do not conflict with any operations performed by the Linkerd sidecars / mesh. Therefore, they can be used alongside one another safely with negligible impact on resources and performance.

First, you must enable sandbox routing using Linkerd by setting the linkerd.enabled helm value to true during the installation of the operator.

Once you have done the above, you can refer to the guide on setting up DevMesh to set up sandbox routing for specific microservices.

Linkerd Custom Labels

Starting in Operator v1.0.0, the helm charts support custom annotations for turning on Linkerd in the Signadot Operator workloads which use Linkerd.

This could have a variety of use cases, including bringing your Linkerd installation custom configuration to the Signadot Operator.

linkerd:
  # Enable the integration with Linkerd
  enabled: true
  operator:
    # Specify custom pod annotations for operator workloads placed on the Linkerd mesh.
    # If the field does not exist, or no annotations are specified, then it will default to
    # linkerd.io/inject: "enabled"
    podAnnotations:
      linkerd.io/inject: enabled
      # EXPERIMENTAL
      config.linkerd.io/proxy-await: enabled