
Automatic merge from submit-queue (batch tested with PRs 50300, 50328, 50368, 50370, 50372) Bugfix: set resources only for fluentd-gcp container. There is more than one container in fluentd-gcp deployment. Previous implementation was setting resources for all containers, not just the fluent-gcp one. **What this PR does / why we need it**: Bugfix; https://github.com/kubernetes/kubernetes/pull/49009 without this is eating more resources. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #50366 **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
Cluster Configuration
Deprecation Notice: This directory has entered maintenance mode and will not be accepting new providers. Please submit new automation deployments to kube-deploy. Deployments in this directory will continue to be maintained and supported at their current level of support.
The scripts and data in this directory automate creation and configuration of a Kubernetes cluster, including networking, DNS, nodes, and master components.
See the getting-started guides for examples of how to use the scripts.
cloudprovider/config-default.sh
contains a set of tweakable definitions/parameters for the cluster.
The heavy lifting of configuring the VMs is done by SaltStack.