Observability with service mesh in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Istio command?

You run the command istioctl proxy-status in your Kubernetes cluster. What does this command show?

Kubernetes

istioctl proxy-status

A Displays the current CPU and memory usage of Istio components.

B Lists all running pods in the cluster with their IP addresses.

C Shows the synchronization status between Istio control plane and Envoy proxies.

D Shows the logs of the Istio ingress gateway.

💡 Hint

Think about what 'proxy-status' might mean in the context of a service mesh.

The istioctl proxy-status command shows if Envoy proxies are synced with the Istio control plane. It helps check if the proxies have the latest configuration.

🧠 Conceptual

intermediate

Why use a service mesh for observability?

Which of the following best explains why a service mesh improves observability in microservices?

A It automatically collects and reports metrics, logs, and traces from service-to-service communication.

B It replaces the need for Kubernetes monitoring tools like Prometheus.

C It encrypts all data stored in the cluster for security.

D It schedules pods to optimize resource usage.

💡 Hint

Observability means understanding what happens inside your system.

A service mesh transparently collects telemetry data like metrics, logs, and traces from the network traffic between services, helping you see how services interact.

❓ Configuration

advanced

Configure Istio to enable distributed tracing

Which YAML snippet correctly enables distributed tracing in Istio by configuring the istio-tracing addon with Jaeger?

A

apiVersion: v1
kind: ConfigMap
metadata:
  name: istio-tracing
  namespace: istio-system
data:
  enabled: "false"

B

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  components:
    ingressGateways:
    - name: istio-ingressgateway
      enabled: false

C

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: tracing
spec:
  hosts:
  - "*"
  http:
  - route:
    - destination:
        host: jaeger

D

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  addonComponents:
    tracing:
      enabled: true
      k8s:
        env:
        - name: JAEGER_ENDPOINT
          value: "http://jaeger-collector.istio-system:14268/api/traces"

💡 Hint

Look for enabling tracing in IstioOperator with correct environment variables.

Option D correctly enables the tracing addon and sets the Jaeger endpoint environment variable for Istio to send traces.

❓ Troubleshoot

advanced

Troubleshoot missing telemetry data in Istio

You notice no telemetry data appears in your monitoring dashboard after deploying Istio. Which of the following is the most likely cause?

A The application containers are running with root user.

B Envoy sidecar proxies are not injected into the application pods.

C The cluster nodes have insufficient CPU resources.

D The Kubernetes API server is down.

💡 Hint

Telemetry depends on proxies capturing traffic.

Istio collects telemetry through Envoy sidecars. If sidecars are missing, no data is collected.

🔀 Workflow

expert

Order the steps to enable observability with Istio service mesh

Arrange these steps in the correct order to enable observability features like metrics and tracing in an Istio-enabled Kubernetes cluster.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about what must be ready before deploying apps and collecting data.

First install Istio with observability enabled, then deploy apps with sidecars, configure monitoring tools, and finally view dashboards.