-
Notifications
You must be signed in to change notification settings - Fork 295
K8s version hardcoded? (... or I am wrong) #1070
Comments
Hi @ivanilves this is the default version, in case you don not override it in cluster.yaml. To upgrade the kubernetes version in a cluster, you have to change the version in cluster.yaml, then render and update the stack using If you intent to use previous versions of kubernetes it's better to also use previous versions of Update: It is also possible to override the container image, for example if you preffer to use Google's hyperkube build. # Version of hyperkube image to use. This is the tag for the hyperkube image repository.
kubernetesVersion: v1.8.5
# Hyperkube image repository to use.
hyperkubeImage:
repo: gcr.io/google-containers/hyperkube-amd64
rktPullDocker: true |
Thanks @camilb ! The thing is that I am trying to install Kubernetes |
@camilb you were right! It works! The error was my own misconfiguration (I was loading wrong 🎉 |
I'm curious, what limitations exist (if any) regarding an upgrade to a more recent version of K8s using |
@drywheat support for Kubernetes 1.9 was added in #1074 here: https://github.com/kubernetes-incubator/kube-aws/pull/1074/files#diff-ef25536c536667a40b993d4d24ab7567R1915, which is not included in v0.9.9. It's a small change, as mentioned in #1076 |
@drywheat I've been using 1.8.7 a lot with kube-aws 0.9.9 without problem. Generally Is expect 1.8.x to work with 0.9.9, since they won't make major API version or component changes. |
Hi guys!
One question:
When I use latest (
v0.9.9
) version ofkube-aws
I always get K8s cluster of version1.8.4
.I also see this line of code in
kube-aws
:https://github.com/kubernetes-incubator/kube-aws/blob/bc100a61283601fa7a82a544f6d8c8f9acf002fc/core/controlplane/config/config.go#L32
Does this mean that with a particular version of
kube-aws
I could only use one specific version of Kubernetes?Does this also mean that to upgrade Kubernetes version on cluster I always need to get new
kube-aws
?... or once deployed with
kube-aws
cluster should be upgraded to new versions of K8s some other way ?Thank you!
The text was updated successfully, but these errors were encountered: