Hands-On Microservices with Kubernetes

Accommodating NATS

One of the limitations I discovered when deploying Istio into the Delinkcious cluster is that NATS doesn't work with Istio because it requires direct connections and it breaks when the Envoy proxy hijacks the communication. The solution is to prevent Istio from injecting the sidecar container and accepting that NATS will not be managed. Adding theNatsCluster CRD to the following annotation to the pod spec does the work for us: sidecar.istio.io/inject: "false":

apiVersion: nats.io/v1alpha2 kind: NatsCluster metadata:   name: nats-cluster spec:   pod:     # Disable istio on nats pods     annotations:       sidecar.istio.io/inject: "false"   size: 1   version: "1.4.0"

The preceding code is the complete NatsCluster resource definition with the annotation ...