[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-08 UTC."],[[["\u003cp\u003eThis guide details the processes for starting, stopping, and checking the status of AlloyDB Omni, whether it's running in a single-server container or a Kubernetes cluster.\u003c/p\u003e\n"],["\u003cp\u003eTo start AlloyDB Omni in a single-server container, use either the \u003ccode\u003edocker container start\u003c/code\u003e or \u003ccode\u003epodman container start\u003c/code\u003e command, replacing \u003ccode\u003e<var translate="no">CONTAINER_NAME</var>\u003c/code\u003e with your container's name.\u003c/p\u003e\n"],["\u003cp\u003eFor Kubernetes deployments, starting and stopping an AlloyDB Omni database cluster involves modifying the \u003ccode\u003eisStopped\u003c/code\u003e field in the cluster's manifest definition using \u003ccode\u003ekubectl\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eYou can connect to an AlloyDB Omni database server running on a single server using its containerized \u003ccode\u003epsql\u003c/code\u003e by executing \u003ccode\u003edocker exec\u003c/code\u003e or \u003ccode\u003epodman exec\u003c/code\u003e, or by connecting with any application that supports PostgreSQL.\u003c/p\u003e\n"],["\u003cp\u003eConnecting to an AlloyDB Omni database cluster in Kubernetes can be done via the pre-installed \u003ccode\u003epsql\u003c/code\u003e within the database pod, or from another pod within the cluster, with secure connections recommended through TLS by specifying a certificate secret.\u003c/p\u003e\n"]]],[],null,[]]
