This message was deleted.
# generala
adamant-kite-43734
02/23/2023, 10:41 PMThis message was deleted.
r
red-waitress-37932
02/24/2023, 4:50 AMYou're downgrading. That's not supported by Kubernetes. Don't do that.
How did you get there?
(Also, please try to use the thread feature and try editing your (unanswered) messages instead of making new ones, to make things more concise and easy to follow)
red-waitress-37932
02/24/2023, 4:54 AMnm about what I wrote at the end of that post. the edit/delete permissions on this server suck majorly
g
gorgeous-daybreak-63660
02/24/2023, 4:19 PMHello BS.
gorgeous-daybreak-63660
02/24/2023, 4:19 PMFirst, I had to create an EKS cluster in rancher with version 1.23 but I wanted to use version 1.24 so what I did was from the AWS console I upgraded from version 1.23 to 1.24, then rancher detected the change and when it finished update the version, mark that error message. When I checked the health of the cluster I saw it was correct, everything is in order, the only thing that was wrong was the error message.
r
red-waitress-37932
02/27/2023, 5:21 AMI don't know what to tell you... did you expect that to work?
red-waitress-37932
02/27/2023, 5:22 AMyou told rancher to create and manage a kubernetes cluster.
then you told AWS to upgrade a cluster that is managed by rancher.
That's not something I personally would expect to work
red-waitress-37932
02/27/2023, 5:24 AMhttps://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/upgrade-and-roll-back-kubernetes here's how you upgrade the cluster through rancher. see if doing that fixes it.
red-waitress-37932
02/27/2023, 5:24 AMif it doesn't, you might have to recreate the cluster from scratch
g
gorgeous-daybreak-63660
02/27/2023, 7:02 PMThank you bro!!!. I had to create the cluster again but with the version 1.23. We work fine with this version at the moment. Thanks for the recommends.
2 Views