921245c828
Automatic merge from submit-queue Remove several red herring error messages in GCE cluster scripts This fixes things like ``` I1018 15:57:53.524] Bringing down cluster W1018 15:57:53.524] NODE_NAMES= W1018 15:57:55.995] ERROR: (gcloud.compute.ssh) could not parse resource: [] W1018 15:57:56.392] ERROR: (gcloud.compute.ssh) could not parse resource: [] ``` and ``` I1018 16:32:34.947] property "clusters.kubernetes-pr-cri-validation_cri-e2e-gce-agent-pr-25-0" unset. I1018 16:32:35.079] property "users.kubernetes-pr-cri-validation_cri-e2e-gce-agent-pr-25-0" unset. I1018 16:32:35.195] property "users.kubernetes-pr-cri-validation_cri-e2e-gce-agent-pr-25-0-basic-auth" unset. I1018 16:32:35.307] property "contexts.kubernetes-pr-cri-validation_cri-e2e-gce-agent-pr-25-0" unset. W1018 16:32:35.420] failed to get client config: Error in configuration: context was not found for specified context: kubernetes-pr-cri-validation_cri-e2e-gce-agent-pr-25-0 ``` It seems like the `kubectl` behavior was introduced in #29236: if `current-context` is set to something invalid, it now complains.
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.