mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-11 06:02:18 +00:00
ff3ca3d616
Automatic merge from submit-queue Pick a specific GCI version by default on GCE. Prior to this change, a K8s branch (master as well as release) was pinned to a GCI milestone. It would pick up the latest GCI release on that milestone at the time of cluster creation. The rationale was the K8s users would automatically get the bug fixes in newer versions of GCI. However in practice, it makes the runtime environment non-deterministic, and lack of continuous e2e tests mean we would run into breakages sooner or later. With this change, each K8s release will pick a specific version of GCI by default (similar to how the Debian-based container-vm gets used). Users can override the default version through KUBE_GCE_MASTER_IMAGE and KUBE_GCE_NODE_IMAGE environment variables. We expect the default GCI version will be updated relatively frequently stay updated with newer GCI releases. We can also automate the process to automatically bump the hard-coded GCI version in future. @vishh @adityakali can you please review? cc @kubernetes/goog-image FYI
Cluster Configuration
Deprecation Notice: This directory has entered maintainence 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.