> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/release-notes/enterprise-operator/26.03/26.03.2.md).
# MariaDB Enterprise Kubernetes Operator 26.03.2
**Release date**: 08 April 2026
If you are running in a version prior to 26.03.x, **please follow the** [**UPDATE GUIDE**](https://mariadb.com/docs/tools/mariadb-enterprise-operator/updates/update-26.03) to ensure a safe transition.
This is a patch release which includes the following fixes:
* **K8SDKR-205**: You can now define container `lifecycle` hooks (`preStop` and `postStart`) directly within the `MaxScale` and `MariaDB` custom resources. The operator automatically propagates these configurations to the reconciled pods. This enhancement enables graceful handling of node drains and termination events, allowing you to drain connections or perform preemptive switchovers without disruption.
* **K8SDKR-194**: You can now define `terminationGracePeriodSeconds` to override the standard 30-second Kubernetes default. By decreasing this value, the kubelet issues a `SIGKILL` sooner during pod termination. This can be leveraged if you want `MaxScale` to detect an offline `MariaDB` container at an earlier stage, significantly reducing overall failover time.
* **K8SDKR-192**: Resolved an issue where `MaxScale` pods could initialize in a partially functional state-configuring servers and monitors, but failing to initialize services and listeners. This occurred under specific runtime conditions, such as the unexpected deletion of `mysql.maxscale_config` or `MaxScale` PVCs. The operator now explicitly includes services and listeners during this initialization phase, ensuring reliable recovery and a fully functional configuration
*This page is: Copyright © 2025 MariaDB. All rights reserved.*
{% @marketo/form formid="4316" formId="4316" %}
---
# 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://mariadb.com/docs/release-notes/enterprise-operator/26.03/26.03.2.md?ask=&goal=
```
`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.