# Release Notes We are excited to introduce Akamas Version 3.2.2, this minor release focus on usability improvements to enhance your optimization experience. As always, we extend our heartfelt thanks to our community of users for their invaluable feedback, which continues to drive the growth and improvement of Akamas. Let's take a closer look at the enhancements in this version! ## Usability Improvements Users can now easily differentiate telemetry instances by providing custom names. The logs of the execution of telemetry instances have been improved and split by instance name to ease the discovery and resolution of configuration issues, particularly in setups with multiple telemetry providers. When deleting a system associated with a running study, users now receive a confirmation prompt to make informed decisions and avoid accidental deletions. Take the most out of your data. Even if the computation of the score fails (e.g. due to a missing key metric), Akamas now computes trial stability windows and aggregated metrics in order to quickly identify the performance of the configuration with respect to other KPIs and constraints. Deploying Akamas on Kubernetes is now a one-liner process. Additionally, we've improved the startup, liveness, and readiness probes for a seamless experience. We value your input and hope these usability improvements empower you to optimize your systems effortlessly. Thank you for choosing Akamas, and we look forward to your feedback as we strive to make Akamas even better in the future! --- # Agent Instructions: 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: ``` GET https://docs.akamas.io/akamas-docs/3.2.2/akamas-reference/release-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.