[[["容易理解","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-04 (世界標準時間)。"],[],[],null,["# Kf reference architecture diagrams\n\nKf can benefit from the rich ecosystem of GKE Enterprise\nand Google Kubernetes Engine (GKE), including automation, managed backing services,\nand development tools.\n\nGKE reference architecture\n--------------------------\n\nKf clusters are managed just like any other\nGKE cluster, and access resources in the same way.\n[](/static/migrate/kf/docs/images/gke-reference-diagram.svg)\n\nConfig Sync\n-----------\n\nKf can work with\n[Config Management](/anthos-config-management/docs/overview) or\nstandalone\n[Config Sync](/anthos-config-management/docs/config-sync-overview) to\nautomate Space creation across any number of clusters. Create\nnew namespaces on non-Kf clusters, and Spaces on\nKf clusters. You can also manage Spaces by\nremoving the Kf CLI from Space management, if desired. Use `kubectl explain` to [get Kf CRD specs](/migrate/kf/docs/2.11/concepts/kf-dependencies#get_crd_details) to fully manage your product configuration via GitOps.\n[](/static/migrate/kf/docs/images/config-sync-reference-diagram.svg)"]]