Disable Service Mesh Sidecar Injection

When SingleStore runs in a Kubernetes cluster that uses a service mesh, sidecar proxy containers may be automatically injected into SingleStore pods. These sidecars can interfere with internal node-to-node communication, health checks, and Operator reconciliation.

Disable sidecar injection for all SingleStore components.

Disable Sidecar Injection for the Operator

In the sdb-operator.yaml file, add the appropriate annotation to the pod template metadata. The following example uses Istio:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: sdb-operator
  labels:
    app.kubernetes.io/component: operator
spec:
  replicas: 1
  selector:
    matchLabels:
      name: sdb-operator
  template:
    metadata:
      annotations:
        sidecar.istio.io/inject: "false"
      labels:
        name: sdb-operator
    spec:
      serviceAccountName: sdb-operator
      containers:
        - name: sdb-operator
          image: operator_image_tag
          ...

Disable Sidecar Injection for SingleStore Pods

In the sdb-cluster.yaml file, add the annotation under objectMetaOverrides for each node specification. Apply the annotation to the Master Aggregator, child aggregators, and leaves.

spec:
  objectOverrides:
    all:
      annotations:
        sidecar.istio.io/inject: "false"
  
  masterAggregatorSpec:
    count: 1
    cores: 4
    coresLimit: 4
    storageGB: 256
    storageClass: standard

  childAggregatorSpec:
    count: 1
    cores: 4
    coresLimit: 4
    storageGB: 256
    storageClass: standard

  leafSpec:
    count: 2
    cores: 8
    coresLimit: 8
    storageGB: 1024
    storageClass: standard

Service Mesh Annotations

The annotation used to disable sidecar injection depends on the service mesh:

Service Mesh

AnnotationAnnotation

Istio

sidecar.istio.io/inject: "false"

Linkerd

linkerd.io/inject: disabled

Consul Connect

consul.hashicorp.com/connect-inject: "false"

Last modified:

Was this article helpful?