> 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/monitoring/appsec-ali-31.md).

# Alibaba Cloud Kubernetes node pools are not set to auto repair misconfiguration detected in code

## Rule Details

|                        |                                  |
| ---------------------- | -------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_ALI\_31                  |
| Category - Subcategory | Kubernetes - Resource Management |
| Provider               | ALIBABA\_CLOUD                   |
| Severity               | LOW                              |
| Framework              | Terraform                        |

## Impact

This rule ensures that Kubernetes node pools in Alibaba Cloud have the auto-repair feature enabled. Auto-repair automatically replaces unhealthy nodes, ensuring high availability and stability of the cluster. This feature helps reduce manual intervention, minimizes downtime, and ensures that workloads are not disrupted by failed nodes.

Failing to enable auto-repair can result in degraded cluster performance or availability if node failures are not promptly addressed.

## How to Fix

*Resource:* alicloud\_cs\_kubernetes\_node\_pool

* *Arguments:* management.auto\_repair

To mitigate this issue, ensure the `management.auto_repair` attribute in the `alicloud_cs_kubernetes_node_pool` resource is set to `true`.

## Example: \[source,go]

resource "alicloud\_cs\_kubernetes\_node\_pool" "example" { ...

management {

* auto\_repair = true } }

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/monitoring/appsec-ali-31.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.