Kubernetes Container Orchestration Helm and Package Management 4

Question 1

What is the purpose of Helm hooks?

Accepted Answer

They execute Kubernetes jobs or other resources at specific points in the release lifecycle

Answer

Helm hooks use annotations like `helm.sh/hook: pre-install` to run Jobs or other resources before/after install, upgrade, or delete.

Question 2

What happens to hook resources after they complete by default?

Accepted Answer

They remain in the cluster and must be manually cleaned up or use hook-delete-policy

Answer

Hook resources persist after completion unless a `helm.sh/hook-delete-policy` annotation specifies `before-hook-creation` or `hook-succeeded`.

Question 3

How do you rollback a Helm release to the previous revision?

Accepted Answer

helm rollback myapp

Answer

`helm rollback <release>` rolls back to the previous revision; specify a revision number like `helm rollback myapp 2` for a specific version.

Question 4

Which Helm command packages a chart directory into a versioned `.tgz` archive?

Accepted Answer

helm package ./mychart

Answer

`helm package` creates a `.tgz` file named `-.tgz` suitable for distribution via a chart repository.

Question 5

What is an OCI-based Helm chart registry?

Accepted Answer

A registry using the OCI (Open Container Initiative) standard to store charts as container artifacts

Answer

Helm 3.8+ supports storing and pulling charts from OCI-compliant registries like Docker Hub, ECR, and GCR using `helm push` and `helm pull oci://`.

Kubernetes Container Orchestration Practice Test