O Config Connector é um complemento do Kubernetes de código aberto que permite gerenciar
recursos doGoogle Cloud pelo Kubernetes.
Muitas equipes de desenvolvimento nativas na nuvem trabalham com uma combinação
de sistemas de configuração, APIs e ferramentas para gerenciar sua infraestrutura. Essa combinação
geralmente é difícil de entender, levando a velocidade reduzida e erros caros. O Config Connector
fornece um método para configurar muitos
serviços e recursos doGoogle Cloud
usando as ferramentas e APIs do Kubernetes.
Com o Config Connector, seus ambientes podem usar
Recursos
gerenciados pelo Kubernetes, incluindo:
RBAC para controle de acesso.
Eventos para visibilidade.
Fonte única de configuração e gerenciamento de estado pretendido para complexidade
reduzida.
Consistência posterior para dependências de acoplamento fraco.
Gerencie sua infraestrutura do Google Cloud da mesma maneira que
gerencia seus aplicativos Kubernetes, reduzindo a complexidade e a carga cognitiva
dos desenvolvedores.
Como funciona o Config Connector
O Config Connector fornece uma coleção de definições de recursos personalizadas
(CRDs, na sigla em inglês) e controladores do Kubernetes. Os CRDs do Config Connector permitem que o Kubernetes crie e
gerencie recursos Google Cloud quando você configura e aplica
objetos ao seu cluster.
Para que os CRDs do Config Connector funcionem corretamente, o Config Connector implanta pods
nos nós que têm permissões elevadas do RBAC, como a capacidade de
criar, excluir, receber e listar CustomResourceDefinitions (CRDs). Essas
permissões são necessárias para que o Config Connector crie e reconcilie recursos do
Kubernetes.
Como personalizar o comportamento do Config Conector
O Config Connector oferece outros recursos além da criação de recursos.
Por exemplo, é possível gerenciar
recursos Google Cloud existentes
e usar secrets do Kubernetes para
fornecer dados sensíveis, como senhas, aos seus recursos. Para mais
informações, consulte a lista de guias de instruções.
Além disso, saiba mais sobre como o Config Connector usa construções do Kubernetes
para gerenciar Recursos e
ver os recursos do Google Cloud
que o Config Connector pode gerenciar.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-11 UTC."],[[["\u003cp\u003eConfig Connector is an open-source Kubernetes add-on that enables the management of Google Cloud resources through Kubernetes APIs and tooling.\u003c/p\u003e\n"],["\u003cp\u003eIt simplifies infrastructure management by allowing teams to use Kubernetes to configure Google Cloud services and resources, reducing complexity and cognitive load.\u003c/p\u003e\n"],["\u003cp\u003eConfig Connector utilizes Kubernetes Custom Resource Definitions (CRDs) and controllers to create and manage Google Cloud resources based on user-defined objects within the cluster.\u003c/p\u003e\n"],["\u003cp\u003eIt provides features such as RBAC, event visibility, single source of configuration, and eventual consistency, enhancing control and management over cloud resources.\u003c/p\u003e\n"],["\u003cp\u003eConfig Connector is open source and includes options to manage pre-existing resources and employ Kubernetes Secrets for confidential data handling.\u003c/p\u003e\n"]]],[],null,["# Config Connector overview\n=========================\n\n[Standard](/kubernetes-engine/docs/concepts/choose-cluster-mode)\n\n*** ** * ** ***\n\nConfig Connector is an [open source](https://github.com/GoogleCloudPlatform/k8s-config-connector) Kubernetes add-on that lets you manage\nGoogle Cloud resources through Kubernetes.\n\nMany cloud-native development teams work with a mix of configuration systems,\nAPIs, and tools to manage their infrastructure. This mix is often difficult to\nunderstand, leading to reduced velocity and expensive mistakes. Config Connector\nprovides a method to configure many\n[Google Cloud services and resources](/config-connector/docs/reference/resources)\nusing Kubernetes tooling and APIs.\n\nWith Config Connector, your environments can use Kubernetes-managed\n[Resources](/config-connector/docs/concepts/resources#managing_resources_with_kubernetes_objects)\nincluding:\n\n- RBAC for access control.\n- Events for visibility.\n- Single source of configuration and desired state management for reduced complexity.\n- Eventual consistency for loosely coupling dependencies.\n\nYou can manage your Google Cloud infrastructure the same way\nyou manage your Kubernetes applications, reducing the complexity and cognitive\nload for developers.\n\nHow Config Connector works\n--------------------------\n\nConfig Connector provides a collection of Kubernetes\n[Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)\n(CRDs) and controllers. The Config Connector CRDs allow Kubernetes to create and\nmanage Google Cloud resources when you configure and apply\nObjects to your cluster.\n\nFor Config Connector CRDs to function correctly, Config Connector deploys Pods\nto your nodes that have elevated RBAC permissions, such as the ability to\ncreate, delete, get, and list CustomResourceDefinitions (CRDs). These\npermissions are required for Config Connector to create and reconcile Kubernetes\nresources.\n\nTo get started,\n[install Config Connector](/config-connector/docs/concepts/installation-types)\nand [create your first resource](/config-connector/docs/how-to/getting-started).\nConfig Connector's\n[controllers](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#custom-controllers)\neventually reconcile your environment with your desired state.\n\n### Customizing Config Connector's behavior\n\nConfig Connector provides additional features beyond creating resources.\nFor example, you can manage\n[existing Google Cloud resources](/config-connector/docs/how-to/managing-deleting-resources#acquiring_an_existing_resource),\nand use [Kubernetes Secrets](/config-connector/docs/how-to/secrets) to\nprovide sensitive data, such as passwords, to your resources. For more\ninformation, see the list of [how-to guides](/config-connector/docs/how-to).\n\nIn addition, you can learn more about how Config Connector uses Kubernetes\nconstructs to manage [Resources](/config-connector/docs/concepts/resources) and\nsee the Google Cloud [resources](/config-connector/docs/reference/resources)\nConfig Connector can manage.\n\nWhat's next\n-----------\n\n- [Install Config Connector](/config-connector/docs/concepts/installation-types).\n- [Get started](/config-connector/docs/how-to/getting-started) by creating your first resource.\n- Explore Config Connector [source code](https://github.com/GoogleCloudPlatform/k8s-config-connector). Config Connector is fully open sourced on GitHub."]]