This message was deleted.
# general
s
This message was deleted.
s
Thanks for sharing the article :) While reading the article, I had a question at this part:
Copy code
Despite making mistakes like updating their Kubernetes cluster before Qovery, which caused production concerns, Qovery's support team remained dedicated and responsive, and this support has become a great strength, fostering trust and confidence for Partoo.
Why was upgrading the K8S version a problem? Was there an upgrade that did not consider the skew? My team also actually upgraded the K8S cluster version a few times, but there were no problems in operation. I would like to refer to your case if possible. Thansk 🙇
r
Hi @Subin Kim, excellent question - since they use Qovery to spin up and fully manage their Kubernetes clusters, it’s up to Qovery to manage the upgrades. We also have an option where they can manage their Kubernetes clusters upgrades on their own, but they didn’t pick that option. So that’s why it was an issue.
s
Aha, that's what it was. I got it. Thank you so much for your kind reply! 🙏 I'll take a look at the doc on how Qovery manages Kubernetes clusters :D
r
Ping me if you have any questions 🙂