Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Scelta di un tipo di installazione
La pagina fornisce una panoramica delle diverse opzioni di installazione
che puoi utilizzare per installare Config Connector.
Puoi installare Config Connector in tre modi:
Config Controller:
Config Controller è un servizio ospitato che include Config Connector. La versione di Config Connector in Config Controller è gestita da Google e aggiornata automaticamente e regolarmente man mano che le versioni diventano idonee.
Config Controller è un piano di controllo centralizzato e designato che offre un modo più sicuro per gestire le risorse. Google Cloud Per ulteriori informazioni, consulta
Guida rapida: gestire le risorse con Config Controller
o Configurare Config Controller.
Componente aggiuntivo Config Connector per GKE:
il componente aggiuntivo Config Connector ti consente di installare Config Connector durante la creazione del cluster.
Il componente aggiuntivo Config Connector è disponibile solo sui cluster GKE Standard e non su Autopilot.
La versione di Config Connector installata tramite il componente aggiuntivo Config Connector è spesso in ritardo di massimo 12 mesi o più. Per ulteriori informazioni, consulta
Upgrade dei componenti aggiuntivi di Config Connector.
Se vuoi ridurre il costo operativo della gestione di un cluster GKE Standard,
considera la possibilità di utilizzare Config Controller.
Esistono molti fattori da considerare quando si seleziona un metodo di installazione. La tabella seguente illustra alcune considerazioni generali:
Metodi di installazione
Vantaggi
Svantaggi
Config Controller
• Nessuna installazione richiesta.
• Upgrade automatici delle versioni.
• Include componenti GitOps predefiniti: Config Sync.
• Gestito e supportato da Google Cloud.
• Limitazione dei carichi di lavoro personalizzati.
• Tariffa di gestione e del cluster.
Installazione manuale
• Completamente personalizzabile.
• Programma di aggiornamento delle versioni flessibile.
• Può essere eseguito con qualsiasi carico di lavoro personalizzato nello stesso cluster.
• Costi operativi.
Componente aggiuntivo Config Connector di GKE
• Ritardo significativo rispetto all'ultima versione di Config Connector.
Autenticazione
Se vuoi installare Config Connector sui cluster GKE, utilizza
Workload Identity Federation for GKE.
La federazione delle identità per i carichi di lavoro per GKE ti consente di configurare un account di servizio Kubernetes per impersonare gli account di servizio Identity and Access Management (IAM) per accedere ai servizi Google Cloud. Config Connector utilizza questo account servizio Kubernetes
all'interno del cluster per creare nuove risorse. Config Connector può creare solo risorse con i ruoli concessi all'account di servizio IAM.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eConfig Connector can be installed in three ways: through Config Controller, manual installation, or as a GKE Config Connector add-on.\u003c/p\u003e\n"],["\u003cp\u003eConfig Controller offers a managed service with automatic updates and built-in GitOps features, but with some restrictions on custom workloads.\u003c/p\u003e\n"],["\u003cp\u003eManual installation provides full customization and flexible version updates but comes with increased operational costs.\u003c/p\u003e\n"],["\u003cp\u003eThe GKE Config Connector add-on is available only on GKE Standard clusters and typically has significant version lag.\u003c/p\u003e\n"],["\u003cp\u003eAuthentication for Config Connector on GKE clusters utilizes Workload Identity Federation, while other deployment options may require Cloud Identity and IAM service account keys, which pose security risks if not properly managed.\u003c/p\u003e\n"]]],[],null,["# Choosing an installation type\n=============================\n\n*** ** * ** ***\n\nThe page provides you with an overview of the different installations options\nyou can use when installing Config Connector.\n\nYou can install Config Connector in one of three ways:\n\n- **[Config Controller](/anthos-config-management/docs/concepts/config-controller-overview)** :\n Config Controller is a hosted service that includes Config Connector. The Config Connector version\n in Config Controller is managed by Google and automatically updated regularly as versions qualify.\n Config Controller is a centralized and designated control\n plane which provides a more secure way to manage Google Cloud resources. For more information, see\n [Quickstart: Manage resources with Config Controller](/anthos-config-management/docs/tutorials/manage-resources-config-controller)\n or [Set up Config Controller](/anthos-config-management/docs/how-to/config-controller-setup).\n\n- **[Manual installation](/config-connector/docs/how-to/install-manually)** :\n To manually install Config Connector, you need to download and use a\n [Kubernetes Operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/).\n Manual installation gives you flexibility on the version you want to apply and when to upgrade.\n If you want to\n [install Config Connector on other Kubernetes distributions](/config-connector/docs/how-to/install-other-kubernetes),\n you need to use a manual installation.\n\n- **[GKE Config Connector add-on](/config-connector/docs/how-to/install-upgrade-uninstall)** :\n The Config Connector add-on lets you install Config Connector during cluster creation.\n The Config Connector add-on is available on only GKE Standard\n clusters, and not [Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview#add-ons).\n The version of Config Connector installed through the Config Connector add-on is often behind by up to 12 months or more. For more information, see\n [Config Connector add-on upgrades](/config-connector/docs/how-to/install-upgrade-uninstall#how-gcp-upgrades-add-on).\n If you want to reduce the operational cost of managing a GKE Standard cluster,\n consider using [Config Controller](/anthos-config-management/docs/concepts/config-controller-overview).\n\nThere are many factors to consider when selecting an installation method. The following table outlines some high-level considerations:\n\nAuthentication\n--------------\n\nIf you want to install Config Connector on GKE clusters, use\n[Workload Identity Federation for GKE](/kubernetes-engine/docs/concepts/workload-identity).\nWorkload Identity Federation for GKE lets you configure a Kubernetes ServiceAccount\nto impersonate Identity and Access Management (IAM) service accounts to access Google Cloud\nservices. Config Connector uses that Kubernetes ServiceAccount\nwithin your cluster to create new resources. Config Connector can only create\nresources with the roles that you grant the IAM service account.\n\nIf you want to install Config Connector on other\n[deployment options](/anthos/deployment-options), such as on-premises or\nmulti-cloud options, use [Cloud Identity](/identity/docs/overview) to\ncreate an account and then use IAM to\n[create a service account key and import the key's credentials as a Secret to your clusters](/iam/docs/keys-create-delete).\n| **Note:** Service account keys are a security risk if not managed correctly. You should [choose a more secure alternative to service account keys](/docs/authentication#auth-decision-tree) whenever possible. If you must authenticate with a service account key, you are responsible for the security of the private key and for other operations described by [Best practices for managing service account keys](/iam/docs/best-practices-for-managing-service-account-keys). If you are prevented from creating a service account key, service account key creation might be disabled for your organization. For more information, see [Managing secure-by-default organization resources](/resource-manager/docs/secure-by-default-organizations).\n|\n|\n| If you acquired the service account key from an external source, you must validate it before use.\n| For more information, see [Security requirements for externally sourced credentials](/docs/authentication/external/externally-sourced-credentials).\n\nManaging resources with service accounts\n----------------------------------------\n\nYou can choose to manage resources with a single service account, or multiple\nservice accounts. If you want to use multiple service accounts, you must\n[install Config Connector in namespaced mode](/config-connector/docs/how-to/install-namespaced).\nFor more information about using IAM service accounts with Config Connector,\nsee [Access control with IAM](/config-connector/docs/how-to/configure-iam-permissions).\n\nWhat's next\n-----------\n\n- Learn how to [manage Google Cloud resources with Config Controller](/anthos-config-management/docs/tutorials/manage-resources-config-controller).\n- Learn how to [manually install Config Connector](/config-connector/docs/how-to/install-manually).\n- Learn how to [install Config Connector as a GKE add-on](/config-connector/docs/how-to/install-upgrade-uninstall).\n- Learn how to [install Config Connector on other Kubernetes distributions](/config-connector/docs/how-to/install-other-kubernetes)."]]