OperatorHub for community operators in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of OperatorHub in Kubernetes?

OperatorHub is a key resource in Kubernetes for managing operators. What is its main role?

A It is a tool to monitor Kubernetes cluster health metrics.

B It provides a centralized catalog to discover and install Kubernetes Operators.

C It manages user authentication and authorization in Kubernetes.

D It automates container image builds and pushes to registries.

💡 Hint

Think about where you find and add new operators to your cluster.

OperatorHub acts as a central place to find and install community and certified Kubernetes Operators, simplifying operator management.

💻 Command Output

intermediate

Output of listing community operators from OperatorHub CLI

What is the expected output of the following command?

kubectl get packagemanifests -n olm

A A list of available operators with their names, versions, and descriptions.

B An error stating 'packagemanifests' resource not found.

C A list of all namespaces in the cluster.

D A list of running pods in the 'olm' namespace.

💡 Hint

Consider what 'packagemanifests' represent in Operator Lifecycle Manager (OLM).

The 'packagemanifests' resource lists all operators available in OperatorHub, showing their metadata.

❓ Configuration

advanced

Configuring OperatorHub to enable a community operator source

You want to enable a community operator source in OperatorHub by editing the OperatorHub custom resource. Which snippet correctly enables the community operators source?

Kubernetes

apiVersion: operators.coreos.com/v1
kind: OperatorHub
metadata:
  name: cluster
spec:
  sources:
  - name: community-operators
    disabled: false

A

spec:
  sources:
  - name: community-operators
    disabled: false

B

spec:
  sources:
  - name: community-operators
    enabled: true

C

spec:
  sources:
  - name: community-operators
    active: true

D

spec:
  sources:
  - name: community-operators
    status: enabled

💡 Hint

Check the correct field name to enable a source in OperatorHub spec.

The OperatorHub spec uses 'disabled: false' to enable a source. Other fields like 'enabled' or 'active' are invalid.

❓ Troubleshoot

advanced

Troubleshooting why a community operator is not visible in OperatorHub UI

You installed a community operator source but it does not appear in the OperatorHub UI. What is the most likely cause?

A The Kubernetes cluster version is too new for OperatorHub to work.

B The user does not have permission to view pods in the 'olm' namespace.

C The operator image is missing from the container registry.

D The community operator source is disabled in the OperatorHub configuration.

💡 Hint

Check the OperatorHub source settings first.

If the community operator source is disabled, its operators won't show in the UI. Permissions or image issues cause different errors.

🔀 Workflow

expert

Steps to add a new community operator to OperatorHub catalog

Arrange the correct order of steps to add a new community operator to the OperatorHub catalog.

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Think about building, publishing, cataloging, then submitting.

The correct workflow is to create the bundle, publish it, add it to the catalog repo, then submit a PR to OperatorHub.