KCNA Helm and Package Management 5

Question 1

What is a Helm library chart and how does it differ from an application chart?

Accepted Answer

A chart that provides reusable templates but deploys no Kubernetes resources itself

Answer

Library charts (type: library in Chart.yaml) define shared template helpers for other charts to use but cannot be installed directly because they produce no manifests.

Question 2

What happens to Helm release history when `helm uninstall` is run without the `--keep-history` flag?

Accepted Answer

All Kubernetes resources and the release history are permanently deleted

Answer

Without `--keep-history`, `helm uninstall` removes both the deployed Kubernetes resources and the release history Secrets, making rollback impossible.

Question 3

Which Helm template function should be used instead of `include` when you need to pipe the result through other functions?

Accepted Answer

include

Answer

`include` returns the rendered string so it can be piped (e.g., `include "mytemplate" . | indent 4`), whereas `template` outputs directly and cannot be piped.

Question 4

What is the role of `helm lint` in chart development?

Accepted Answer

Statically checks a chart for common errors, misconfigurations, and best-practice violations

Answer

`helm lint` performs static analysis on a chart directory, reporting errors and warnings about structure, required fields, and template issues before deployment.

Question 5

When using `helm upgrade` with `--atomic`, what occurs if the upgrade fails?

Accepted Answer

The upgrade is automatically rolled back to the previous successful release

Answer

`--atomic` combines `--wait` with automatic rollback: if any resource fails to become ready within the timeout, Helm rolls the release back to its previous revision.

(KCNA) Kubernetes and Cloud Native Associate Practice Test

(KCNA) Kubernetes and Cloud Native Associate Practice Test

KCNA Helm and Package Management 5