-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.11 -> 1.12 upgrade docs #684
Labels
Comments
@christopherhein would you like to do this? |
@christopherhein I've pushed 887f097 assuming you have nothing to add, but please config. |
It would be nice to document if |
It currently uses the EKS API directly, we have
#683 track that.
…On Tue, 2 Apr 2019, 9:04 pm Aaron Roydhouse, ***@***.***> wrote:
It would be nice to document if eksctl 0.1.27 uses the CloudFormation
support for upgrading the cluster
<aws/containers-roadmap#115 (comment)>?
Or does it bypass the CF stack and user the EKS API? I was holding off
upgrading because I didn't want the control plane CF stack to drift and not
be usable.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#684 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPWS8n-v7XrWM-QgSUV-Y7SY0NfxuC_ks5vc7fWgaJpZM4cSvQz>
.
|
pawelprazak
pushed a commit
to VirtusLab/eksctl
that referenced
this issue
Apr 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We haven't updated the readme after #680 landed, we should do it soon. The main part is addition of
update-coredns
command, but it's worse documenting that one has to upgrade one version at a time.The text was updated successfully, but these errors were encountered: