[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-04-11。"],[[["\u003cp\u003eThis guide pertains exclusively to Kubernetes-based AlloyDB Omni deployments, not single-server setups.\u003c/p\u003e\n"],["\u003cp\u003eAlloyDB Omni operator sidecar containers, distinct from built-in Kubernetes sidecars, run alongside the main application in the same Pod and can be used for monitoring, logging, and tracing.\u003c/p\u003e\n"],["\u003cp\u003eYou can manually add a sidecar container to an existing AlloyDB Omni deployment by creating and applying a sidecar custom resource (CR) to your database cluster.\u003c/p\u003e\n"],["\u003cp\u003eAdding or modifying a sidecar container on an active database will result in a restart of the Pod it runs on, potentially causing downtime.\u003c/p\u003e\n"],["\u003cp\u003eTo register a sidecar container to your database cluster, use the \u003ccode\u003ekubectl patch\u003c/code\u003e command and specify the database cluster name and the sidecar CR name.\u003c/p\u003e\n"]]],[],null,[]]