(D) This method is often recommended for upgrading Kubernetes clusters. It involves creating a new cluster with the desired Kubernetes version and then migrating workloads to the new cluster. This approach minimizes downtime and avoids potential risks associated with in-place upgrades or rolling upgrades. While 'rolling upgrade' is a valid concept in some contexts, but it typically applies to upgrading individual components or workloads within a cluster, rather than upgrading the cluster itself. Rolling upgrades can be risky for the entire cluster, as they may lead to inconsistencies or downtime during the process.
Tanzu Kubernetes clusters are upgraded using a rolling upgrade method, where new virtual machines with the upgraded Kubernetes version replace the running nodes, starting with the control plane nodes. Instead of upgrading the Kubernetes versions directly on the existing nodes, new virtual machines with the new version are deployed, and they gradually replace the running nodes
That's not technically correct. While a new cluster with the TKr gets created, Tanzu follows the "Rolling Upgrade" method while upgrading a cluster, this is used to avoid downtime in the cluster/apps hosted in.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
kl0ud
4 days, 16 hours agoNano76
1 month agoNEOEDGE
6 months agototto1230
5 months, 3 weeks agototto1230
5 months, 3 weeks agocontributor
6 months, 1 week agocontributor
6 months, 1 week agocontributor
6 months, 1 week agocontributor
6 months, 1 week ago