Event inspection for diagnostics in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to list all events in the default namespace.

Kubernetes

kubectl get [1]

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

Apods

Bservices

Cnodes

Devents

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pods' instead of 'events' will list pods, not events.

Using 'nodes' or 'services' will show unrelated resources.

The kubectl get events command lists all events in the current namespace, which is default if not specified.

2fill in blank

medium

Complete the command to describe a specific event named 'my-event'.

Kubernetes

kubectl describe [1] my-event

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

Aevent

Bpod

Cservice

Dnode

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pod' or 'service' will try to describe the wrong resource type.

Using 'node' will describe a node, not an event.

The kubectl describe event my-event command shows detailed information about the event named 'my-event'.

3fill in blank

hard

Fix the error in the command to get events from the 'kube-system' namespace.

Kubernetes

kubectl get events -n [1]

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

Adefault

Bdev

Ckube-system

Dproduction

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' will show events from the default namespace, not 'kube-system'.

Using 'production' or 'dev' may cause errors if those namespaces don't exist.

The -n kube-system flag specifies the 'kube-system' namespace to get events from that namespace.

4fill in blank

hard

Fill both blanks to filter events by reason 'Failed' in the 'default' namespace.

Kubernetes

kubectl get events -n [1] --field-selector reason=[2]

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

Adefault

Bkube-system

CFailed

DStarted

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong namespace will show no or unrelated events.

Using 'Started' instead of 'Failed' will filter different events.

Use -n default to specify the namespace and --field-selector reason=Failed to filter events with reason 'Failed'.

5fill in blank

hard

Fill all three blanks to create a JSON output of events filtered by type 'Warning' in 'kube-system' namespace.

Kubernetes

kubectl get events -n [1] --field-selector type=[2] -o [3]

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

Adefault

Bkube-system

CWarning

Djson

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' namespace will not show system events.

Using 'Started' instead of 'Warning' filters wrong event types.

Forgetting '-o json' outputs default table format.

Use -n kube-system for the namespace, --field-selector type=Warning to filter warning events, and -o json to output in JSON format.