[[["易于理解","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-09-05。"],[[["\u003cp\u003eThe current Apigee hybrid documentation version (1.5) is end-of-life and should be upgraded to a newer version for continued support and security.\u003c/p\u003e\n"],["\u003cp\u003eA typical Apigee hybrid installation comprises multiple pods, each with specific port access requirements and communication patterns, as detailed in the internal connections documentation.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid includes various pods such as \u003ccode\u003eapigee-logger\u003c/code\u003e, \u003ccode\u003eapigee-metrics\u003c/code\u003e, \u003ccode\u003eapigee-cassandra\u003c/code\u003e, \u003ccode\u003eapigee-synchronizer\u003c/code\u003e, \u003ccode\u003eapigee-udca\u003c/code\u003e, \u003ccode\u003eapigee-mart\u003c/code\u003e, and \u003ccode\u003eapigee-runtime\u003c/code\u003e each with its own purpose.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends implementing Kubernetes network policies to restrict communication between pods and to manage external access, utilizing resources like the Kubernetes \u003ccode\u003eNetworkPolicy\u003c/code\u003e resource and open-source CNI plugins like Calico.\u003c/p\u003e\n"]]],[],null,["# Securing the runtime installation\n\n| You are currently viewing version 1.5 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nA typical Apigee hybrid installation is made of multiple pods, as listed in the\nfollowing table.\nEach of these pods require specific access to ports, and not every pod needs to communicate\nwith every other pod. For a detailed map of these internal connections and the security\nprotocols they employ, see [Internal connections](/apigee/docs/hybrid/v1.5/ports#internal).\n\n\nGoogle recommends that you follow these methods and best practices to harden,\nsecure, and isolate the runtime\npods:"]]
