> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-k8s-44.md).

# Tiller (Helm v2) service is not deleted misconfiguration detected in code

## Rule Details

|                        |                                                        |
| ---------------------- | ------------------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_K8S\_44                                        |
| Category - Subcategory | Kubernetes - Management Services Exposure              |
| Provider               | OTHER                                                  |
| Severity               | LOW                                                    |
| Framework              | Helm, Kubernetes, Kustomize, Terraform, Terraform Plan |

## Impact

Tiller (Helm v2) is the in-cluster component of Helm. It interacts directly with the Kubernetes API server to install, upgrade, query, and remove Kubernetes resources. It also stores the objects that represent releases. Its permissive configuration could grant the users a broad range of permissions. Helm v3 removes Tiller, and it is recommended that you upgrade: see link:doc:bc\_k8s\_32\[Ensure Tiller (Helm V2) Is Not Deployed]. However, this is not always feasible. Restricting access to Tiller from within the cluster limits the abilities of a compromised pod or anonymous user in the cluster. After link:doc:bc\_k8s\_40\[restricting connectivity to the Tiller deployment], the Tiller service can be deleted.

## How to Fix

*Resource:* Service

***

## \[source,go]

{ "-- apiVersion: v1

* kind: Service
* metadata:
* labels:
* app: helm
* name: tiller
* name: tiller-deploy
* namespace: kube-system
* spec:
* ports:
* * name: tiller
* port: 44134
* protocol: TCP
* targetPort: tiller
* selector:
* app: helm
* name: tiller
* type: ClusterIP", }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-k8s-44.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.