OperatorHub for community operators in Kubernetes - Step-by-Step Execution

Process Flow - OperatorHub for community operators

User wants an Operator

↓

Access OperatorHub

↓

Search for Community Operator

↓

Select Operator

↓

Install Operator

↓

Operator runs in cluster

↓

User manages apps with Operator

This flow shows how a user finds and installs a community operator from OperatorHub to manage apps in Kubernetes.

Execution Sample

Kubernetes

kubectl get packagemanifests -n olm
kubectl create -f community-operator-subscription.yaml
kubectl get csv -n operators
kubectl get pods -n operators

Commands to list available operators, install a community operator, check its status, and see running pods.

Process Table

Step	Command	Action	Result
1	kubectl get packagemanifests -n olm	List all operators in OperatorHub	Shows list including community operators
2	kubectl create -f community-operator-subscription.yaml	Subscribe to community operator	Subscription created, Operator install starts
3	kubectl get csv -n operators	Check ClusterServiceVersion status	CSV shows 'Succeeded' when operator is ready
4	kubectl get pods -n operators	Check operator pods running	Operator pod is Running
5	User uses operator to manage apps	Operator manages app lifecycle	Apps deployed and managed by operator
6	-	End of flow	Operator installed and ready

💡 Operator installed and running, ready to manage applications

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Operator List	empty	list of operators including community	same	same	same	same
Subscription Status	none	none	created	active	active	active
CSV Status	none	none	none	Succeeded	Succeeded	Succeeded
Operator Pod Status	none	none	none	none	Running	Running

Key Moments - 3 Insights

Why do we check the CSV status after creating the subscription?

Because the CSV status shows if the operator installation succeeded. Step 3 in the execution table shows checking CSV to confirm readiness.

What does the subscription resource do?

It tells Operator Lifecycle Manager to install and manage the operator. Step 2 shows creating the subscription to start installation.

Why check pods after CSV is succeeded?

Because the operator runs as pods. Step 4 confirms the operator pod is running, meaning the operator is active.

Visual Quiz - 3 Questions

Look at the execution table, what is the CSV status at Step 3?

A Pending

B Failed

C Succeeded

D Unknown

💡 Hint

Check the 'Result' column for Step 3 in the execution table.

At which step does the operator pod become Running?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Result' column for Step 4 in the execution table.

If the subscription is not created, what will happen to the CSV status?

A It will show 'Succeeded'

B It will remain 'none' or not exist

C It will show 'Failed'

D It will show 'Running'

💡 Hint

Refer to the variable_tracker row for 'CSV Status' before Step 3.

Concept Snapshot

OperatorHub lets you find and install community operators in Kubernetes.
Use 'kubectl get packagemanifests -n olm' to list operators.
Create a Subscription resource to install an operator.
Check CSV status to confirm installation success.
Verify operator pods are running to ensure operator is active.

Full Transcript

OperatorHub is a place where Kubernetes users can find community operators to help manage applications. The user first lists available operators using kubectl. Then, they create a subscription to install the chosen operator. The ClusterServiceVersion (CSV) resource shows if the operator installed successfully. Finally, checking the operator pods confirms the operator is running and ready. This process helps users add new capabilities to their Kubernetes clusters easily.