This ensures that we're using our settings for downloading nodeup
itself and any assets that nodeup downloads. This is a workaround for
reported problems with the initial download on some kernels otherwise.
Issue #10206
We pass the appropriate flag to curl / wget, but where it fails we
fall back to not using compression.
Also simplify the code paths here, as it has proven so tricky - we
simply try a sequence of commands until we successful download and a
hash match.
We were previously assuming that the name of the URL matched the name
we wanted to download to, but also assuming that the name of the file
was nodeup. Change to download to a known file location, whatever the
mirror url.
There was a regression in apimachinery which meant that kubernetes
tolerated field names with incorrect case. Upstream bug is
https://github.com/kubernetes/kubernetes/issues/64612
Syncing up with latest kubernetes will mean we get the same breaking
change as kubernetes has/had. It should only affect people that are
manually building YAML / JSON.
Added as a significant item to release notes.
The current implementation does not ignore any possible interpolation of bash in the content. This PR wrapped the various spec content in 'EOF' to ignore all.
- updated the tests to reflect the changes
- wrapped the component configuration in 'eof' to ensure interpolation is ignored
* Detect CoreOS
* Move key manifests to code, to tolerate read-only mounts
* Misc refactorings so more code can be shared
* Change lots of ints to int32s in the models
* Run nodeup as a oneshot systemd service, rather than relying on
cloud-init behaviour which varies across distros
* Zones are now subnets
* Utility subnet is no longer part of Zone
* Bastion InstanceGroup type added instead
* Etcd clusters defined in terms of InstanceGroups, not zones
* AdminAccess split into SSHAccess & APIAccess
* Dropped unused Multizone flag