[[["容易理解","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-05 (世界標準時間)。"],[[["\u003cp\u003eApigee hybrid installations consist of multiple pods, each with specific functions like logging (\u003ccode\u003eapigee-logger\u003c/code\u003e), metrics (\u003ccode\u003eapigee-metrics\u003c/code\u003e), persistence (\u003ccode\u003eapigee-cassandra\u003c/code\u003e), synchronization (\u003ccode\u003eapigee-synchronizer\u003c/code\u003e), analytics (\u003ccode\u003eapigee-udca\u003c/code\u003e), administration (\u003ccode\u003eapigee-mart\u003c/code\u003e), and request processing (\u003ccode\u003eapigee-runtime\u003c/code\u003e).\u003c/p\u003e\n"],["\u003cp\u003ePods within the Apigee hybrid installation have specific port access requirements, and not all pods need to communicate with each other, as detailed in the internal connections map.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends reviewing the Google Kubernetes Engine (GKE) security overview and cluster hardening guidelines to secure the Kubernetes infrastructure.\u003c/p\u003e\n"],["\u003cp\u003eNetwork policies can be used to manage communication between pods, allowing restrictions on access, and isolation of pods from the outside network.\u003c/p\u003e\n"],["\u003cp\u003eUsing a container network interface (CNI) such as Calico allows the addition of network policies to the hybrid runtime.\u003c/p\u003e\n"]]],[],null,["# Securing the runtime installation\n\n| You are currently viewing version 1.13 of the Apigee hybrid documentation. 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.13/ports#internal).\n\n\nGoogle recommends that you follow these methods and best practices to harden,\nsecure, and isolate the runtime\npods:"]]
