Closed sonnysideup closed 7 years ago
@drywheat Thanks for the report!
AFAICS by reading code, releaseChannel
under worker.nodePools[]
doesn't seem to work because it is not implemented at all!
It is a bug that the key is mentioned in the cluster.yaml.
Anyways, I guess we can make releaseChannel
per node pool pretty easily.
I think this addition would be useful. It will allow operations teams to run a heterogeneous mix of Container Linux servers (alpha/beta/stable) is various quantities, which is what CoreOS actually recommends. 😃
Versions
kube-aws: v0.9.7 kubernetes: v1.6.3+coreos.0
Synopsis
I am currently using the CoreOS stable release channel for most of my cluster but I would like to configure my CICD node pool to use the alpha channel; this has a newer version of Docker that supports staged-builds. Adding the following configuration lines to
cluster.yaml
and runningkube-aws update
affects no change whatsoever. In AWS, I see the top-level CF stack for the cluster check for an update and then exit immediately thereafter.I tried to (1) create a new node pool using the alpha channel and (b) updating an existing node pool to use alpha channel. In both cases the node pool ended up using the stable channel.
Please let me know if I can provide any further information.