-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade to K8S 1.19 LTS (1.16 is EOL) #51
Labels
Comments
nikhiljha
changed the title
Upgrade to K8S 1.19 LTS (1.15 is EOL)
Upgrade to K8S 1.19 LTS (1.16 is EOL)
Aug 28, 2020
closer ocf/puppet#1019 |
Will doing everything #59 wants also resolve this or is this a completely separate issue? |
I don't see anything that would magically upgrade k8s there
…On Thu, Oct 22, 2020 at 16:51 Ronit Nath ***@***.***> wrote:
Will doing everything #59 <#59>
wants also resolve this or is this a completely separate issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#51 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFTUFHBERAU4NUQUE74FC3SMDAQDANCNFSM4QMVR2ZA>
.
|
Isn't the old cluster still around and on 1.16? |
yeah but it doesn't look like that will ever be updated |
Sure, but I wouldn't say we're upgraded then really, not unless the 1.16 cluster is gone... |
Soon :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Night pointed out that our version of Kubernetes is very very old. I ran into some issues with deploying serverless functions because of this.
This version of k8s will be supported for 1 year rather than 9 months like prior kubernetes versions.
The text was updated successfully, but these errors were encountered: