[[["わかりやすい","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 UTC。"],[],[],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.9/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)"]]