Exam AZ-400 topic 8 question 18 discussion

Helm 3 supports a new chart format and no longer installs the Tiller server-side component.

"chart" is not an answer. Helm packages **were and are** called "charts", and in order to deploy a chart (using the devops Helm Task), you do not need to deploy some "chart" service. Helm 3 uses K8S Secrets as well as the Standard API, so the Tiller Service is now obsolete. Try it - you do not have to install anything into the cluster before using the Helm-Task in devops. This is simply an old question, and if MS really still uses it, "Tiller" would still be the only sensible answer assuming we're talking Helm 2.

Tiller was previously part of Helm for managing releases in Helm v2 but has been removed in Helm v3. Since Helm v3, Tiller is no longer needed, and kubectl is used for direct communication with the Kubernetes API.

Since Tiller has been deprecated in Helm version 3 and later, you no longer need to install Tiller in your AKS cluster.

Tiller service

The correct answer is D. Tiller. Tiller is an in-cluster component of Helm which interacts with the Kubernetes API server to install, upgrade, query, and remove Kubernetes resources. It manages the deployment of Charts, which are packages of pre-configured Kubernetes resources, and is used in conjunction with the Helm package and deploy task in Azure DevOps to deploy applications to an AKS cluster.

To deploy to an Azure Kubernetes Services (AKS) cluster using the Helm package and deploy task, you would need to install the Helm Tiller service in the AKS namespace. Helm is a package manager for Kubernetes that allows you to manage Kubernetes applications by using a simple YAML file, called a Chart. Tiller is the server-side component of Helm that runs inside the Kubernetes cluster and manages the installation, upgrade, and removal of Charts.

https://www.bmc.com/blogs/kubernetes-helm-charts/# "Helm Charts are simply Kubernetes YAML manifests combined into a single package that can be advertised to your Kubernetes clusters" https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/helm-deploy?view=azure-devops "You can use the task to install or update Tiller to a Kubernetes namespace" Answer is D

D is correct answer.

Correct

The question asks: "Which service should you install". Chart is not a service but a package, so I suppose this is another old question with old answer options. Tiller should be the correct answer even if it is not used anymore on helm 3

the given answer is correct

Make sense that it's B check link from vglearn

This question should specify what Helm version was installed on target server to answer correctly, is it was Helm 2 tiller was the correct answer, if it was Helm v3 no service is needed to install

Tiller, Verified. Source:https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/helm-deploy?view=azure-devops

Per Microsoft, "The Helm package and deploy task can be used to package the app and deploy it to a Kubernetes cluster. You can use the task to install or update Tiller to a Kubernetes namespace, to securely connect to Tiller over TLS for deploying charts, or to run any Helm command such as lint." https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/helm-deploy?view=azure-devops

You need to install a service in the AKS namespace. Which service should you install? Answer is A: Azure Container Registry. (Here is why?) What most people don't realize is you don't need a separate repo for Helm charts. You store Helm Charts along with the base container images in ACR. That is what you need to configure. Where to get the containers & apps, that helm charts are trying to install. Tiller is Only applicable to Helm 2 & below. Helm 3 is the current.