> For the complete documentation index, see [llms.txt](https://docs.onyxia.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyxia.sh/contributors-doc/community-calls/august-2025-community-call.md). # August 2025 community call Community call 08/28/2025 ## Project news * Release v10.27 * Onboarding as a separate go module (test it, `onboarding.enabled=true` in your values : ) * State of go : * Onboarding is functional and at (almost, mainly missing events support) parity with current API * Work is now on `services` API * Code is available on a monorepo : * Feedback and contributions welcome ! #dev-rewrite-to-go on slack to discuss * Bitnamigate happening today :scream: : * Bitnami dropping / reducing docker & helm charts availability and support * Inseefrlab (defaults for Onyxia) catalogs have been updated this week to use `bitnamilegacy` (mainly for databases catalog) * Future : we will try to remove catalog dependencies to bitnami wherever and whenever it's feasible --- # 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://docs.onyxia.sh/contributors-doc/community-calls/august-2025-community-call.md?ask=&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.