It also covers what “integrations” mean in the context of your control plane. The section below covers what it means to configure each of these. runtime configuration, such as ProviderConfigs or EnvironmentConfigs.integrations, and the configuration of those integrations.
At a high level, you can think about the configuration of your control plane as boiling down to: In this repository, you should put all configurations applicable to your control plane. The Git repository should contain the definition for your control plane’s configuration. Upbound recommends using a Git repository hosted on a version control service as the single source of truth. Reference the provider’s documentation for specific recommendations. Upbound recommends at least four to eight CPU cores, depending on the provider. For example, the Upbound provider-aws-ec2 installs 98 CRDs. Each CRD installed requires about 4 MB of memory in the control plane pod. The number of CRDs installed by the providers determines the resource requirements. You can right-size the nodes where your Kubernetes cluster control plane runs. If you deploy Crossplane on a self-hosted Kubernetes cluster, you have control over the resource allocations. Microsoft automatically scales control plane node without any required changes. Microsoft Azure Kubernetes Service (AKS) doesn’t require any configuration when running Upbound providers. During this time the Kubernetes API server may be unavailable to handle new requests. Smaller clusters take at least 40 minutes to stabilize. Testing by Upbound finds that GKE clusters configured with at least 20 nodes don’t have issues. Google Kubernetes Engine (GKE) sizes their control plane nodes based on the total number of nodes deployed in a cluster.
Amazon automatically scales control plane node without any required changes. Amazon Elastic Kubernetes ServiceĪmazon Elastic Kubernetes Service (EKS) doesn’t require any configuration when running Upbound providers. As a result, each managed Kubernetes provider handles the resource needs of Upbound providers differently. In managed Kubernetes environments such as AWS EKS or GCP GKE, you don’t control the Kubernetes control plane nodes. They help you avoid installing CRDs that you don’t need on your control plane and mitigates concerns about Crossplane being CRD-hungry. With provider families supported starting in Crossplane v1.12 and Upbound Official Provider Families released, we strongly recommend users adopt these providers.
0 kommentar(er)
