Terraform-aws-eks: EKS - k8s v.1.2 upgrade
I have issues
I'm submitting a...
- [ ] bug report
- [x] feature request
- [ ] support request
- [ ] kudos, thank you, warm fuzzy
AWS news
chenrui333
All 8 comments
when you change cluster_version=>1.12, it will automatically upgrade.
We might change the default value if needed. As far as I know, there is nothing else to "fix" !?
EDIT: FYI, it took 20m57s
confiq
on 29 Mar 2019
how was like upgrading from v1.10 to v1.11?
chenrui333
on 29 Mar 2019
Never did that...
confiq
on 29 Mar 2019
ok. I think there is already a PR for the upgrade: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/327
chenrui333
on 29 Mar 2019
ok, 1.10 -> 1.11 is pretty much the same, :)
module.eks.aws_eks_cluster.this: Modifications complete after 21m38s
chenrui333
on 29 Mar 2019
PR was merged. Update your module version to latest commit ID or wait a few days for a new release 馃檪
max-rocket-internet
on 3 Apr 2019
This actually only upgrades the EKS control plane, right?
Does the upgrade process with this module cause downtime?
syst0m
on 31 May 2019
This actually only upgrades the EKS control plane, right?
Correct. You can see when it's done as the Server Version in kubectl version will change.
Does the upgrade process with this module cause downtime?
Nope. In theory the k8s API will be done for a small amount of time but this doesn't affect running nodes or pods in a negative way.
After updating EKS you can update your nodes to a newer AMI.
max-rocket-internet
on 31 May 2019
Related issues
mattlawnz
路
3Comments
jimmiebtlr
路
3Comments
discordianfish
路
3Comments
tnimni
路
3Comments
Pratima
路
4Comments
Most helpful comment
Correct. You can see when it's done as the Server Version in
kubectl versionwill change.Nope. In theory the k8s API will be done for a small amount of time but this doesn't affect running nodes or pods in a negative way.
After updating EKS you can update your nodes to a newer AMI.