> 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/appsec2-gcp-19.md).

# GCP Kubernetes Engine Clusters have Alpha cluster feature enabled misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_GCP\_19                      |
| Category - Subcategory | Kubernetes - Native Security Controls |
| Provider               | GCP                                   |
| Severity               | LOW                                   |
| Framework              | Terraform, Terraform Plan             |
| Mapped CSPM/KSPM Rule  | 7153b3ac-dc68-4f88-a981-db2992b81a80  |

## Impact

The rule is checking to ensure that the 'alpha cluster' feature is disabled in Google Cloud Platform's (GCP) Kubernetes engine clusters. This is important because enabling the alpha cluster feature can present several potential issues.

First, it reduces stability: Alpha features are not stable and are likely to change in future Kubernetes versions, which can cause disruptions to the functioning of deployed applications. Second, it increases security risks: These features are not subject to the same level of scrutiny as stable API versions, so their usage can inadvertently expose the cluster to potential security vulnerabilities. Lastly, it can lead to poor resource management because some alpha features might consume more resources than stable features — leading to inefficiency and increased costs. For these reasons, it's important to disable the 'alpha cluster' feature in GCP Kubernetes engine clusters.

## How to Fix

*Resource:* google\_container\_cluster

* *Arguments:* enable\_kubernetes\_alpha

In order to fix the issue, you have to make sure that the 'enable\_kubernetes\_alpha' option is set to false for all GCP Kubernetes Engine Clusters. This can be done using the following Terraform code:

## The above code makes sure that the 'alpha cluster' feature is disabled. Google GKE alpha clusters are based on the alpha version of the GKE API, which is not recommended for production use as it includes features that are not fully tested, and may undergo significant changes in terms of stability, security, and breaking changes. Therefore, production environments should always use GKE standard clusters which are stable and secure. \[source,go]

resource "google\_container\_cluster" "my\_cluster" { name = "my-cluster"

...

## enable\_kubernetes\_alpha = false }


---

# 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/appsec2-gcp-19.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.