
ICA (Istio Certified Associate) is the Linux Foundation and CNCF certification for Istio, the most widely used service mesh on Kubernetes. Istio adds traffic control, mutual TLS, authorisation and telemetry between microservices without changing application code. The exam is partly performance-based: you install and configure Istio and fix problems on a real cluster, so lab practice matters more than reading. It suits DevOps, platform and SRE engineers who already know Kubernetes basics.
This guide follows the official Linux Foundation exam page: the four domains with weights, sidecar vs ambient mode, the resources you will write (Gateway, VirtualService, DestinationRule, PeerAuthentication, AuthorizationPolicy), a 4-week lab plan and 15 original practice questions.
Quick facts (Linux Foundation, November 2026)
| Item | Detail |
|---|---|
| Format | Online, proctored, performance-based and multiple choice |
| Duration | 2 hours |
| Prerequisites | None (Kubernetes experience strongly recommended) |
| Price | US$250 exam only; US$299 with the LFS245 course; US$495 with an annual training subscription |
| Validity | 2 years |
| Eligibility | 12 months to schedule and take the exam; one retake included |
Read the official ICA exam page and check the candidate handbook for the Istio version used in the exam environment.
Domains and weights
| Domain | Weight | Objectives (from the Linux Foundation) |
|---|---|---|
| Traffic Management | 35% | Ingress and egress; routing in the mesh; traffic policies with DestinationRules; traffic shifting; connecting to external workloads and services; resilience (circuit breaking, failover, outlier detection, timeouts, retries); fault injection |
| Securing Workloads | 25% | Authorisation; authentication (mTLS, JWT); securing edge traffic with TLS |
| Installation, Upgrade and Configuration | 20% | Installing with istioctl or Helm; sidecar or ambient mode; customising the installation; canary and in-place upgrades |
| Troubleshooting | 20% | Configuration; the control plane; the data plane |
Sidecar vs ambient mode
| Sidecar mode | Ambient mode |
|---|---|
| An Envoy proxy container is injected into every pod | No sidecars: a per-node ztunnel handles mTLS and L4; optional waypoint proxies handle L7 features |
Enable with the label istio-injection=enabled on a namespace, then restart pods | Enable with the label istio.io/dataplane-mode=ambient on a namespace |
| Full L7 features for every pod; more memory and CPU per pod | Lower overhead; add a waypoint only where L7 routing or policy is needed |
Resources you must be able to write
# Send 90% of traffic to v1 and 10% to v2, with a timeout and retries
apiVersion: networking.istio.io/v1
kind: VirtualService
metadata: { name: reviews }
spec:
hosts: [reviews]
http:
- route:
- destination: { host: reviews, subset: v1 }
weight: 90
- destination: { host: reviews, subset: v2 }
weight: 10
timeout: 3s
retries: { attempts: 3, perTryTimeout: 1s }
---
# Subsets plus circuit breaking / outlier detection
apiVersion: networking.istio.io/v1
kind: DestinationRule
metadata: { name: reviews }
spec:
host: reviews
subsets:
- { name: v1, labels: { version: v1 } }
- { name: v2, labels: { version: v2 } }
trafficPolicy:
connectionPool: { tcp: { maxConnections: 100 } }
outlierDetection: { consecutive5xxErrors: 5, interval: 30s, baseEjectionTime: 60s }
---
# Require mTLS for every workload in the namespace
apiVersion: security.istio.io/v1
kind: PeerAuthentication
metadata: { name: default, namespace: shop }
spec:
mtls: { mode: STRICT }
---
# Only the frontend service account may call the payments service with GET or POST
apiVersion: security.istio.io/v1
kind: AuthorizationPolicy
metadata: { name: payments-allow-frontend, namespace: shop }
spec:
selector: { matchLabels: { app: payments } }
action: ALLOW
rules:
- from: [ { source: { principals: ["cluster.local/ns/shop/sa/frontend"] } } ]
to: [ { operation: { methods: ["GET", "POST"] } } ]
Also know Gateway (or the Kubernetes Gateway API) for ingress and egress, ServiceEntry for external services, RequestAuthentication for JWT validation, and the fault block in a VirtualService for delay and abort injection.
Troubleshooting commands
istioctl analyze -n shop # find config mistakes
istioctl proxy-status # are proxies in sync with istiod?
istioctl proxy-config routes deploy/frontend -n shop
istioctl x describe pod <pod> -n shop # which rules apply to this pod
kubectl logs deploy/istiod -n istio-system
4-week lab plan
| Week | Focus | Lab (kind or minikube) |
|---|---|---|
| 1 | Install with istioctl and Helm, profiles, sidecar vs ambient, canary upgrade with revisions | Install Istio, deploy the Bookinfo sample, then do a revision-based upgrade |
| 2 | Gateways, VirtualServices, DestinationRules, traffic shifting, ServiceEntry and egress | Do a 90/10 canary, then mirror traffic; allow one external API through egress |
| 3 | Resilience and fault injection; mTLS (PERMISSIVE vs STRICT), JWT, AuthorizationPolicy, TLS at the gateway | Inject a 5-second delay and fix it with a timeout; lock down one service to one caller |
| 4 | Troubleshooting control and data plane; timed practice | Break five configs on purpose and fix them with istioctl; book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. Which Istio component is the control plane?
istiod.
2. Which proxy does Istio use in sidecar mode?
Envoy.
3. You labelled a namespace for sidecar injection but pods have no sidecar. What did you forget?
Restart (re-create) the existing pods; injection happens at pod creation.
4. In ambient mode, which component handles mTLS and L4 traffic on each node?
ztunnel.
5. Which resource defines subsets such as v1 and v2?
DestinationRule.
6. Which resource splits traffic 80/20 between subsets?
VirtualService (weighted routes).
7. How do you let mesh workloads call an external payment API by hostname?
A ServiceEntry for that host (and egress gateway rules if egress is locked down).
8. Which setting ejects a pod that keeps returning 5xx errors?
outlierDetection in a DestinationRule.
9. How do you test how the app behaves when the ratings service is slow, without changing code?
Fault injection with a delay in the VirtualService.
10. During migration some clients don't have sidecars yet. Which mTLS mode avoids breaking them?
PERMISSIVE.
11. Which resource validates JWTs on incoming requests?
RequestAuthentication (combined with an AuthorizationPolicy to require a valid token).
12. An AuthorizationPolicy with action ALLOW exists for a workload. What happens to requests that match no rule?
They are denied.
13. What is the safest way to upgrade Istio in production?
A canary upgrade with revisions, moving namespaces to the new revision one at a time.
14. Which command reports whether every proxy has the latest configuration from istiod?
istioctl proxy-status.
15. Which command checks your Istio configuration for common errors?
istioctl analyze.
After ICA
- Strengthen the basics with KCNA, CKAD and KCSA.
- Add progressive delivery with the Argo CAPA and observability with OTCA.
- Learn it hands-on in our Kubernetes course; see live DevOps and platform jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches Kubernetes, service mesh, DevSecOps and multi-cloud DevOps with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the ICA exam?
The Linux Foundation and CNCF Istio Certified Associate: an online, proctored exam with performance-based and multiple-choice questions on Istio.
How long is the ICA exam?
2 hours.
Which ICA domain has the most weight?
Traffic Management at 35%, followed by Securing Workloads at 25%.
Does ICA cover ambient mode?
Yes. Installing Istio in sidecar or ambient mode is an objective.
Does ICA have prerequisites?
No formal prerequisites, but Kubernetes experience is strongly recommended.
How long is ICA valid?
2 years.



