[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-09 (世界標準時間)。"],[[["\u003cp\u003eThis document details version 1.9 of the Apigee hybrid documentation, which covers the components and security of a typical Apigee hybrid installation.\u003c/p\u003e\n"],["\u003cp\u003eThe Apigee hybrid installation consists of multiple pods, including \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 specific functions.\u003c/p\u003e\n"],["\u003cp\u003eTo enhance security, it is recommended to use Kubernetes network policies to control communication between pods and manage external access.\u003c/p\u003e\n"],["\u003cp\u003eReviewing the Google Kubernetes Engine (GKE) security overview is recommended for a detailed look into security configuration options within the Kubernetes infrastructure.\u003c/p\u003e\n"],["\u003cp\u003eImplement a Container Network Interface (CNI) plugin like Calico to add network policies, to isolate pods and control their access.\u003c/p\u003e\n"]]],[],null,["# Securing the runtime installation\n\n| You are currently viewing version 1.9 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.9/ports#internal).\n\n\nGoogle recommends that you follow these methods and best practices to harden,\nsecure, and isolate the runtime\npods:"]]
