community icon indicating copy to clipboard operation
community copied to clipboard

[EKS] POC for skip version upgrades

Open vijtrip2 opened this issue 3 years ago • 2 comments

The EKS service mandates that each version upgrade can only increment the cluster by 1 minor version - such as 1.17. to 1.18. If you try to upgrade by more than that, it will return an error. The EKS controller should support being able to declare the desired version and make the incremental minor version updates on the user's behalf. That is, if the current version is 1.17 and the desired is 1.20, then the controller should increment to 1.18, 1.19and then finally1.20`. Since each of these upgrades can take some time, the resource may be out of sync for a while, but it should eventually resolve.

vijtrip2 avatar Jun 24 '22 16:06 vijtrip2

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

eks-bot avatar Sep 22 '22 22:09 eks-bot

/remove-lifecycle stale

a-hilaly avatar Sep 23 '22 12:09 a-hilaly

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

ack-bot avatar Feb 09 '23 03:02 ack-bot

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

ack-bot avatar Mar 11 '23 07:03 ack-bot

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

ack-bot avatar Jun 13 '23 21:06 ack-bot

Issues go stale after 180d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 60d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

ack-bot avatar Dec 11 '23 12:12 ack-bot

Stale issues rot after 60d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 60d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

ack-bot avatar Feb 09 '24 13:02 ack-bot

Implemented in https://github.com/aws-controllers-k8s/eks-controller/releases/tag/v1.3.0 /close

a-hilaly avatar Feb 09 '24 17:02 a-hilaly

@a-hilaly: Closing this issue.

In response to this:

Implemented in https://github.com/aws-controllers-k8s/eks-controller/releases/tag/v1.3.0 /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

ack-prow[bot] avatar Feb 09 '24 17:02 ack-prow[bot]