Helm Interview Questions Hindi mein

Helm कोर्स के 25 सवाल, हर सवाल के सही जवाब और explanation के साथ। जवाब देखने से पहले ख़ुद सोचें।

Why Helm and Core Ideas

1. Which capability does Helm add that plain `kubectl apply` of files lacks?

  1. Tracking a set of objects as one versioned release that can be rolled back
  2. Running containers
  3. Scheduling pods onto nodes
  4. Building container images
जवाब देखें

जवाब: Tracking a set of objects as one versioned release that can be rolled back

Helm groups manifests into a release with revision history; scheduling and running containers is still Kubernetes' job.

पाठ: The Problem Helm Solves

2. Where does Helm 3 store the record of each release revision by default?

  1. In a Tiller pod in kube-system
  2. In a local file in your home directory only
  3. In the chart repository
  4. As Secrets in the release's namespace
जवाब देखें

जवाब: As Secrets in the release's namespace

Helm 3 removed Tiller and stores release revisions as Secrets in the namespace of the release.

पाठ: Charts, Releases, Repositories and Values

3. Which command shows the configurable settings of a chart before you install it?

  1. helm status
  2. helm history
  3. helm show values
  4. helm get manifest
जवाब देखें

जवाब: helm show values

helm show values prints the chart's default values.yaml, documenting what you can configure.

पाठ: Your First Install

Configuring and Upgrading Releases

4. A value is set in values.yaml, in values-prod.yaml passed with -f, and with --set. Which wins?

  1. values.yaml
  2. values-prod.yaml
  3. The --set value
  4. Whichever is alphabetically first
जवाब देखें

जवाब: The --set value

--set overrides values files, which override the chart defaults.

पाठ: Values Files and Overrides

5. Why add --wait to helm upgrade in a CI pipeline?

  1. It makes rendering faster
  2. So the command fails if workloads do not become ready, instead of reporting success too early
  3. It skips hooks
  4. It deletes old revisions
जवाब देखें

जवाब: So the command fails if workloads do not become ready, instead of reporting success too early

Without --wait Helm succeeds once objects are accepted, even if the new pods never become ready.

पाठ: Upgrades, History and Rollbacks

6. How do you install a chart from an OCI registry?

  1. helm install NAME oci://registry/path/chart --version X
  2. helm repo add, then helm install repo/chart
  3. kubectl apply -f oci://...
  4. helm pull is required before any install
जवाब देखें

जवाब: helm install NAME oci://registry/path/chart --version X

OCI charts are referenced directly by an oci:// URL; no repo add step is needed.

पाठ: Repositories and OCI Registries

Anatomy of a Chart

7. What does the `version` field in Chart.yaml describe?

  1. The version of the chart itself
  2. The Kubernetes version
  3. The application's container image tag only
  4. The Helm CLI version
जवाब देखें

जवाब: The version of the chart itself

version is the chart's SemVer; appVersion describes the application being deployed.

पाठ: Chart Layout and Chart.yaml

8. Why does the generated template wrap `replicas` in `if not .Values.autoscaling.enabled`?

  1. Replicas are not allowed in Deployments
  2. To speed up rendering
  3. Because Helm cannot set integers
  4. So the HorizontalPodAutoscaler, not Helm, controls the replica count when autoscaling is on
जवाब देखें

जवाब: So the HorizontalPodAutoscaler, not Helm, controls the replica count when autoscaling is on

If Helm kept setting replicas, every upgrade would fight the HPA's chosen count.

पाठ: Scaffolding with helm create

9. Which command renders manifests locally without contacting the cluster?

  1. helm upgrade --wait
  2. helm rollback
  3. helm template
  4. helm status
जवाब देखें

जवाब: helm template

helm template renders charts offline; dry runs of install/upgrade can contact the cluster.

पाठ: Rendering, Linting and Dry Runs

Templating Language

10. What does `{{-` (with a dash) do?

  1. Subtracts one from a value
  2. Comments out the line
  3. Trims whitespace and newlines to the left of the action
  4. Marks the value as required
जवाब देखें

जवाब: Trims whitespace and newlines to the left of the action

The dash trims whitespace on that side of the action, keeping rendered YAML tidy.

पाठ: Template Basics and Built-in Objects

11. Inside a `range` block, how do you read the release name?

  1. .Release.Name
  2. $.Release.Name
  3. range.Release.Name
  4. It is not possible
जवाब देखें

जवाब: $.Release.Name

range rebinds the dot to the current item; $ always refers to the root context.

पाठ: Conditionals, Loops and Scope

12. Why is `include` preferred over the `template` action in Helm charts?

  1. include returns a string that can be piped to functions such as nindent
  2. include is faster
  3. template is removed in Helm 3
  4. include works only in values.yaml
जवाब देखें

जवाब: include returns a string that can be piped to functions such as nindent

include's output can be piped, which is needed to indent or transform snippets.

पाठ: Named Templates, include and tpl

Dependencies, Hooks and Validation

13. How does a parent chart set the `auth.database` value of a dependency called postgresql?

  1. In postgresql.auth.database in the parent's values
  2. In global.auth.database only
  3. By editing the subchart's files in charts/
  4. Subcharts cannot be configured
जवाब देखें

जवाब: In postgresql.auth.database in the parent's values

Values nested under the subchart's name are passed to that subchart.

पाठ: Subcharts and Dependencies

14. Which annotation makes a pod run only when you execute `helm test`?

  1. helm.sh/hook: post-install
  2. helm.sh/hook-weight: test
  3. helm.sh/resource-policy: keep
  4. helm.sh/hook: test
जवाब देखें

जवाब: helm.sh/hook: test

Pods annotated with helm.sh/hook: test run on demand through helm test.

पाठ: Hooks and Chart Tests

15. What happens to CRDs in a chart's crds/ directory when you run helm upgrade?

  1. They are upgraded to the new definition
  2. They are deleted and recreated
  3. They are not upgraded; Helm only installs them on first install
  4. They are converted to templates
जवाब देखें

जवाब: They are not upgraded; Helm only installs them on first install

Helm installs crds/ content once and never upgrades or deletes it, to protect custom resources.

पाठ: Values Schemas, CRDs and Library Charts

Chart Quality, Testing and Security

16. Which approach validates rendered manifests against Kubernetes schemas without a cluster?

  1. helm rollback
  2. helm status
  3. helm template piped to kubeconform
  4. kubectl get pods
जवाब देखें

जवाब: helm template piped to kubeconform

Rendering offline and validating with kubeconform catches invalid fields and API versions early.

पाठ: Testing Charts

17. Why is putting a database password directly in a values file risky?

  1. Helm cannot render passwords
  2. It is stored in the release record and often committed to Git, visible to many people
  3. Kubernetes rejects plain-text values
  4. It makes the chart larger than the limit
जवाब देखें

जवाब: It is stored in the release record and often committed to Git, visible to many people

Values are persisted in release records and usually version control, widening who can read the secret.

पाठ: Secrets and Supply-Chain Security

18. Which practice keeps a chart portable across namespaces?

  1. Letting the release namespace decide instead of hardcoding it
  2. Hardcoding metadata.namespace: production
  3. Putting every value under global
  4. Using the template action instead of include
जवाब देखें

जवाब: Letting the release namespace decide instead of hardcoding it

Hardcoded namespaces break installs into other namespaces and confuse Helm's release tracking.

पाठ: Chart Best Practices

Delivering with Helm

19. What should change when promoting a release from staging to production?

  1. Only the environment-specific values and target cluster
  2. The chart version and the image, rebuilt for production
  3. The chart's templates
  4. Nothing; production uses staging's cluster
जवाब देखें

जवाब: Only the environment-specific values and target cluster

Promote the same chart and image; differences between environments belong in values.

पाठ: Managing Environments

20. Why does a chart deployed by Argo CD usually not appear in `helm list`?

  1. Argo CD deletes Helm releases
  2. helm list only shows OCI charts
  3. Argo CD uses Helm 2
  4. Argo CD renders the chart and applies the manifests itself instead of creating a Helm release
जवाब देखें

जवाब: Argo CD renders the chart and applies the manifests itself instead of creating a Helm release

Argo CD uses Helm as a templating step and manages the resulting objects directly.

पाठ: GitOps with Argo CD and Flux

21. In a chart pipeline, what should happen before a new chart package is pushed?

  1. Nothing; push on every commit with the same version
  2. Delete the old chart from the registry
  3. Lint, render and validate it, and make sure the chart version was bumped
  4. Run helm rollback
जवाब देखें

जवाब: Lint, render and validate it, and make sure the chart version was bumped

Validation catches broken charts, and a version bump keeps published versions immutable.

पाठ: Chart CI/CD Pipelines

Operating Helm in Practice and Revision

22. A CI job was cancelled during an upgrade and the release now shows pending-upgrade. What is the usual fix?

  1. Delete the namespace
  2. Run helm repo update
  3. Roll back to the last successful revision
  4. Edit the release Secret by hand
जवाब देखें

जवाब: Roll back to the last successful revision

Rolling back to a known-good revision clears the pending state through a normal Helm operation.

पाठ: Troubleshooting Releases

23. Which feature does Kustomize lack compared with Helm?

  1. Per-environment patches
  2. Release history with rollback and chart packaging
  3. Plain YAML bases
  4. Integration with kubectl
जवाब देखें

जवाब: Release history with rollback and chart packaging

Kustomize patches YAML but does not package charts or keep a release history.

पाठ: Helm, Kustomize and Plain Manifests

24. Why might a CI service account with only namespace-level permissions fail to install a third-party chart?

  1. The chart creates cluster-scoped objects such as CRDs or ClusterRoles
  2. Helm requires cluster-admin for every install
  3. Namespaces cannot hold Helm releases
  4. OCI registries require cluster-admin
जवाब देखें

जवाब: The chart creates cluster-scoped objects such as CRDs or ClusterRoles

Cluster-scoped resources need cluster-level RBAC, which namespace-scoped deployers do not have.

पाठ: Helm in Shared Clusters

25. In Helm, what does `helm upgrade --install` do when the release does not exist yet?

  1. Fails with release not found
  2. Creates only the namespace
  3. Runs helm template and exits
  4. Installs it, so the same command works for first and later deployments
जवाब देखें

जवाब: Installs it, so the same command works for first and later deployments

--install makes upgrade install the release when it is missing, which suits idempotent pipelines.

पाठ: Helm Revision and Interview Questions

← कोर्स पर वापस जाएँ