Istio overview in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to install Istio's base components using Istioctl.

Microservices

istioctl install --set profile=[1] -y

Drag options to blanks, or click blank then click option'

Ademo

Bminimal

Cdefault

Dcustom

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'minimal' profile which installs fewer components.

Using 'default' profile which installs fewer demo features.

The demo profile installs Istio with default features suitable for learning and testing.

2fill in blank

medium

Complete the command to label the default namespace for automatic sidecar injection.

Microservices

kubectl label namespace default istio-injection=[1]

Drag options to blanks, or click blank then click option'

Ayes

Btrue

Cenabled

Dauto

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'true' which is not the correct label value.

Using 'yes' or 'auto' which are invalid values.

The label value enabled tells Istio to inject sidecars automatically in the namespace.

3fill in blank

hard

Fix the error in the command to check Istio pods in the istio-system namespace.

Microservices

kubectl get pods -n [1]

Drag options to blanks, or click blank then click option'

Aistio-system

Bistio

Ckube-system

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' namespace which usually holds user workloads.

Using 'kube-system' which is for Kubernetes system components.

Istio components run in the istio-system namespace by default.

4fill in blank

hard

Fill both blanks to create a virtual service routing HTTP traffic to the productpage service.

Microservices

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: productpage
spec:
  hosts:
  - [1]
  http:
  - route:
    - destination:
        host: [2]

Drag options to blanks, or click blank then click option'

Aproductpage.default.svc.cluster.local

Bproductpage

Creviews

Ddetails

Attempts:

3 left

💡 Hint

Common Mistakes

Using short names in both places causing routing errors.

Using wrong service names like 'reviews' or 'details'.

The hosts field uses the full service domain name, while the destination.host uses the short service name.

5fill in blank

hard

Fill all three blanks to define a destination rule with load balancing set to round robin.

Microservices

apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: [1]
spec:
  host: [2]
  trafficPolicy:
    loadBalancer:
      simple: [3]

Drag options to blanks, or click blank then click option'

Aproductpage

Breviews

Cround_robin

DroundRobin

Attempts:

3 left

💡 Hint

Common Mistakes

Using snake_case 'round_robin' which is invalid.

Using different names for rule and host causing mismatch.

The destination rule name and host should match the service name. The load balancer simple type for round robin is roundRobin (camelCase).