[[["わかりやすい","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-01 UTC。"],[],[],null,["# Isolate the Agones controller in your GKE cluster\n\n[Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\n[Agones](https://agones.dev/site/docs/overview/) is an open source\nlibrary for hosting, running, and scaling dedicated game servers on Kubernetes.\nWhen you run a production deployment of Agones in your\nGoogle Kubernetes Engine (GKE) cluster, it is a [best\npractice](https://agones.dev/site/docs/guides/best-practices/#separation-of-agones-from-gameserver-nodes)\nto run the Agones controller in a dedicated node pool for better isolation and\nresiliency. This is best suited for production workloads or\ncost-optimized workloads.\n\nGKE monitors your clusters and uses the [Recommender\nservice](/recommender/docs/overview) to deliver guidance for how you can\noptimize your usage of the platform. The *Agones Recommender* for\nGKE identifies clusters where you should isolate the Agones\ncontroller.\n\nTo learn more about how to manage insights and recommendations from\nRecommenders, see [Optimize\nyour usage of GKE with insights and recommendations](/kubernetes-engine/docs/how-to/optimize-with-recommenders).\n\nIdentify clusters where you can isolate the Agones controller\n-------------------------------------------------------------\n\nThe insights from the *Agones Recommender* identify which clusters\ncontain an Agones controller that should be isolated in a dedicated node pool.\n\nTo get these insights, follow the instructions to [view insights and recommendations](/kubernetes-engine/docs/how-to/optimize-with-recommenders#view-insights-recs)\nusing the Google Cloud console, the Google Cloud CLI, or the Recommender API with\nthe `AGONES_DEDICATED_NODE_POOL_NEEDED` subtype.\n\nAfter you identify the clusters, you can [implement the recommendation to create a dedicated node pool](#create-dedicated-node-pool).\n\nHow GKE Agones Recommender detects clusters\n-------------------------------------------\n\nThe Recommender generates an insight and recommendation if the\nfollowing criteria are true for a GKE cluster:\n\n- The cluster is running an Agones controller. This is determined if any Pods have the `agones.dev/role:controller` label set.\n- The cluster has more than four nodes, which is an indicator that the cluster might be running a production workload.\n- The Agones controller is not running on the dedicated node for Agones. A dedicated node pool is considered to be one that has the following node label `agones.dev/agones-system=true` and node taint `agones.dev/agones-system=true:NoExecute`.\n\nImplement the recommendation to create a dedicated node pool\n------------------------------------------------------------\n\nIf you've received an insight and recommendation for your cluster and want to\nuse a dedicated node pool for your Agones controller, follow the instructions\nto [create a dedicated node pool](https://agones.dev/site/docs/installation/creating-cluster/gke/#optional-creating-a-dedicated-node-pool) where your Agones controller can be scheduled.\n\nThe Recommender runs once daily so it might take up to 24\nhours for the recommendation to resolve after changes have been\nimplemented.\n\nIf you don't want to implement the recommendation, you can [dismiss\nit](/kubernetes-engine/docs/how-to/optimize-with-recommenders#dismiss-recommendation).\n\nWhat's next\n-----------\n\n- [Optimize your usage of GKE with insights and\n recommendations](/kubernetes-engine/docs/how-to/optimize-with-recommenders)\n- [Create a GKE cluster for your Agones\n install](https://agones.dev/site/docs/installation/creating-cluster/gke/)"]]