> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.9/support.md). # Support In the underlying support pages, we provide valuable information about Platform9's dedicated Kubernetes service and world-class support we provide that empowers customer success via our Certified Kubernetes Administrators and experienced solutions experts. Our team members are well versed on all facets of Kubernetes and are ready to assist you if and when help is needed. Our well-organized support teams are trained and equipped to handle almost any complex issues that may arise with Kubernetes, and the various components its related ecosystem. We have years of in-depth experience helping new, intermediate and experienced customers, including enterprise level clients successfully adopt Kubernetes infrastructures across multiple platforms. We can assist with things like: * Kubernetes Architecture Consulting * Implementation & Execution * Migration Strategies * Deployment Planning * DevOps Schemes * Cost Optimization * Ongoing Support Models If you happen to run into an issue, please do not hesitate to [reach out to us for assistance](https://support.platform9.com/hc/en-us/requests/new?ticket_form_id=360000924873). We are here to help! --- # 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.platform9.com/managed-kubernetes/5.9/support.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.