Refactor upgrade docs #7668
Merged
Refactor upgrade docs #7668
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eks-distro-bot
added
the
size/L
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7668 +/- ##
==========================================
+ Coverage 73.48% 73.61% +0.12%
==========================================
Files 579 588 +9
Lines 36357 37149 +792
==========================================
+ Hits 26718 27346 +628
- Misses 7875 8012 +137
- Partials 1764 1791 +27 ☔ View full report in Codecov by Sentry. |
taneyland
reviewed
Feb 23, 2024
docs/content/en/docs/clustermgmt/cluster-upgrades/baremetal-upgrades.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/baremetal-upgrades.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/baremetal-upgrades.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/baremetal-upgrades.md
Outdated
Show resolved
Hide resolved
taneyland
reviewed
Feb 23, 2024
docs/content/en/docs/clustermgmt/cluster-upgrades/upgrade-overview.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/vsphere-and-cloudstack-upgrades.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/vsphere-and-cloudstack-upgrades.md
Outdated
Show resolved
Hide resolved
csplinter
force-pushed
the
docs-refactor-upgrades
branch
from
e145683 to
afe58b3
Compare
d8660091
reviewed
Feb 23, 2024
docs/content/en/docs/clustermgmt/cluster-upgrades/upgrade-overview.md
Outdated
Show resolved
Hide resolved
d8660091
reviewed
Feb 23, 2024
docs/content/en/docs/clustermgmt/cluster-upgrades/upgrade-overview.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/upgrade-overview.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/upgrade-overview.md
Outdated
Show resolved
Hide resolved
docs/content/en/docs/clustermgmt/cluster-upgrades/upgrade-overview.md
Outdated
Show resolved
Hide resolved
|
|
||
| If you are using an Kubernetes API-compatible client, you modify your workload cluster spec yaml and apply the modified yaml to your management cluster. The EKS Anywhere lifecycle controller, which runs on the management cluster, reconciles the desired changes on the workload cluster. | ||
|
|
||
| As of EKS Anywhere version `v0.19.0`, management components can be upgraded separately from cluster components. This is enables you to get the latest updates to the management components such as Cluster API controller, EKS Anywhere controller, and provider-specific controllers without impact to your workload clusters. Management components can only be upgraded with the `eksctl anywhere` CLI, which has new `eksctl anywhere upgrade plan management-components` and `eksctl anywhere upgrade management-component` commands. For more information, reference the [Upgrade management components page.]({{< relref "./management-components-upgrade" >}}) |
There was a problem hiding this comment.
Suggested change
| As of EKS Anywhere version `v0.19.0`, management components can be upgraded separately from cluster components. This is enables you to get the latest updates to the management components such as Cluster API controller, EKS Anywhere controller, and provider-specific controllers without impact to your workload clusters. Management components can only be upgraded with the `eksctl anywhere` CLI, which has new `eksctl anywhere upgrade plan management-components` and `eksctl anywhere upgrade management-component` commands. For more information, reference the [Upgrade management components page.]({{< relref "./management-components-upgrade" >}}) | |
| As of EKS Anywhere version `v0.19.0`, management components can be upgraded separately from cluster components. This is enables you to get the latest updates to the management components such as Cluster API controller, EKS Anywhere controller, and provider-specific controllers without impact to your workload clusters. Management components can only be upgraded with the `eksctl anywhere` CLI, which has new `eksctl anywhere upgrade plan management-components` and `eksctl anywhere upgrade management-component` commands. For more information, reference the [Upgrade Management Components page.]({{< relref "./management-components-upgrade" >}}) |
|
|
||
| ### Upgrading Kubernetes Versions | ||
|
|
||
| Each EKS Anywhere version supports at least 4 minor versions of Kubernetes. Kubernetes patch version increments are included in EKS Anywhere minor and patch releases. There are two places in the cluster spec where you can configure the Kubernetes version, `Cluster.Spec.KubernetesVersion` and `Cluster.Spec.WorkerNodeGroupConfiguration[].KubernetesVersion`. If only `Cluster.Spec.KubernetesVersion` is set, then that version will apply to both control plane and worker nodes. You can use `Cluster.Spec.WorkerNodeGroupConfiguration[].KubernetesVersion` to upgrade your worker nodes separately from control plane nodes. The `Cluster.Spec.WorkerNodeGroupConfiguration[].KubernetesVersion` cannot be greater than `Cluster.Spec.KubernetesVersion`. |
There was a problem hiding this comment.
cannot be greater than
Cluster.Spec.KubernetesVersion
Should we call out the minimum version the worker nodes can be as well?
drewvanstone
approved these changes
Feb 28, 2024
taneyland
approved these changes
Feb 28, 2024
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherrypick release-0.19 |
|
@csplinter: new pull request created: #7732 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.