summaryrefslogtreecommitdiffstats
path: root/utils/test
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2017-10-24 20:04:02 -0700
committerGitHub <noreply@github.com>2017-10-24 20:04:02 -0700
commitc6bde33f155ed6c0c7d7edfd78678f912131e86f (patch)
tree4e3b77bbd36d49d8480d3dc08a99ce931f0c6c12 /utils/test
parentf0da12b7292cddabfc7c33206cabf0ff34aa9852 (diff)
parent5547e39983a154829c56df0961eeab54c3933bd4 (diff)
downloadopenshift-c6bde33f155ed6c0c7d7edfd78678f912131e86f.tar.gz
openshift-c6bde33f155ed6c0c7d7edfd78678f912131e86f.tar.bz2
openshift-c6bde33f155ed6c0c7d7edfd78678f912131e86f.tar.xz
openshift-c6bde33f155ed6c0c7d7edfd78678f912131e86f.zip
Merge pull request #5780 from smarterclayton/allow_per_node_group_bootstrap_and_image
Automatic merge from submit-queue. Handle bootstrap behavior in GCP template Allow each node group to request bootstrap, allow per node group image override, and ensure the provision logic does not wait for bootstrapping node groups before continuing. This is an incremental step to allow GCP clusters to use bootstrap logic on cluster deploy without having fully baked images. We will switch over slowly and ensure both code paths function. Then we can remove this as necessary. For metadata, we set the cluster id and bootstrap state into instance metadata. On GCP, we'll use project metadata to set the bootstrap kubeconfig file and a startup-script to call it (not in a PR yet). Pairs with openshift/origin-gce#54 @kwoodson
Diffstat (limited to 'utils/test')
0 files changed, 0 insertions, 0 deletions