- Linkerd has automatic protocol and TCP connection detection.
A) True
B) False
- Linkerd uses its own Ingress controller.
A) True
B) False
- The Linkerd proxy is written in
GO
, while the control plane components are written in Rust.
A) True
B) False
- The control and data plane can be in a single namespace if so desired.
A) True
B) False
- When a Linkerd proxy is injected using the linkerd inject command to a running pod, pods are restarted automatically.
A) True
B) False
- You can add a debug sidecar to a microservice without having to restart the pod.
A) True
B) False
- The retry budget helps us avoid a retry storm, and we don't need to do any configuration in Linkerd to achieve this.
A) True
B) False
- For automatic sidecar injection, Istio needs a labeled namespace with istio-injection=enabled, while Linkerd needs a namespace annotated with linkerd.io/inject: Enabled.
A) True
B) False
- istio-init and linkerd-init are run before the sidecar proxy to set the entries in iptables to route the application pod traffic through the sidecar proxy.
A) True
B) False
- We can use the Istio and Linkerd sidecars as an edge proxy.
A) True
B) False
- Horizontal pod autoscaling for the control plane for Istio and Linkerd is automatic.
A) True
B) False