-
Notifications
You must be signed in to change notification settings - Fork 37
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
Clarify Kubernetes Support Lifecycle #2013
Conversation
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 35.9%, saving 53.23 KB.
585 images did not require optimisation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiny comments 🚀
Co-authored-by: Adelina Simion <[email protected]>
* docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review Co-authored-by: Adelina Simion <[email protected]> * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]> (cherry picked from commit 51aaad2)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made suggestions on structure, word usage, and some other small things. Hope it's helpful, and congrats on the doc 🎉
|
||
### Support Lifecycle | ||
|
||
We support other Kubernetes distributions such as K3s, Microk8s, and RKE2 until their official EOL. The EOL is set by the respective owner. Once we stop supporting the minor version, we initiate the deprecation process. You can learn more about our Kubernetes support lifecycle in the [Kubernetes Support Lifecycle](./kubernetes-support.md#other-kubernetes-distributions) page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be "on the Kubernetes Support Lifecycle page." Reference.
|
||
## Overview | ||
|
||
We follow a similar lifecycle as established by the Kubernetes community. You can learn more about the official supported Cloud Native Computing Foundation (CNCF) Kubernetes release cycle in the [Kubernetes Releases](https://kubernetes.io/releases/) page. This means we support three minor Kubernetes versions at any given time. We support the current release and the three previous minor version releases, also known as N-3. For example, if the current release is 1.29, we support 1.28, 1.27, and 1.26. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd want to simplify this, as in:
Our support for Kubernetes aligns with the official Kubernetes release cycle. Meaning that at any given time, we support the current Kubernetes release and the three previous minor version releases (also known as N-3). For example, if the current release is 1.29, we support 1.28, 1.27, and 1.26.
--- | ||
sidebar_label: "Kubernetes Support Lifecycle" | ||
title: "Kubernetes Support Lifecycle" | ||
description: "Learn about the Kubernetes versions we support and how we manage Kubernetes support." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd want to avoid repetition here:
Learn how we support the Kubernetes Lifecycle.
|
||
:::info | ||
|
||
Kubernetes follows the [semantic version schema](https://semver.org/). Versions are annotated as x.y.z, where x is the major version, y is the minor version, and z is the patch version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be semantic versioning schema? Also, for me it would make sense to emphasize versioning notation with bold, as in:
** x.y.z**, where x is..., y is..., and z is...
Kubernetes follows the [semantic version schema](https://semver.org/). Versions are annotated as x.y.z, where x is the major version, y is the minor version, and z is the patch version. | ||
::: | ||
|
||
We support N-3 Kubernetes minor versions until the official End-Of-Life (EOL). Once we stop supporting the minor version, we initiate the deprecation process. You can learn more about our deprecation process in the [Pack Deprecation](./maintenance-policy.md#pack-deprecations) section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we don't stop supporting a specific version, but rather a version, it feels like "a" would be more appropriate here. Also, to me deprecation is a process, so it feels a bit redundant to add "process" here.
Once we stop supporting a minor version, we initiate its deprecation.
|
||
## Other Kubernetes Distributions | ||
|
||
We support other Kubernetes distributions such as K3s, Microk8s, and RKE2 until their official EOL. The EOL is set by the respective owner. Once we stop supporting the minor version, we initiate the deprecation process. You can learn more about our deprecation process in the [Pack Deprecation](./maintenance-policy.md#pack-deprecations) section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once we stop supporting the minor version, we initiate the deprecation process. You can learn more about our deprecation process in the Pack Deprecation section.
This also repeats what you've mentioned in the Overview section. Maybe, consider making it an admonition that calls attention to this process for all Kubernetes versions and distros?
|
||
## Kubernetes Upgrades | ||
|
||
The official guidelines for Kubernetes upgrades recommend upgrading one minor version at a time. For example, if you are using Kubernetes version 1.26, you should upgrade to 1.27, before upgrading to version 1.28. You can learn more about the official Kubernetes upgrade guidelines in the [Version Skew Policy](https://kubernetes.io/releases/version-skew-policy/) page. We |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to add a link here? Especially given that we're explicitly recommending readers to follow these guidelines.
The official guidelines for Kubernetes upgrades
:::tip | ||
|
||
Use cluster profile versions to manage your Kubernetes upgrades. Create a new cluster profile version for each Kubernetes upgrade. You can then use the new cluster profile version to upgrade your cluster. | ||
|
||
::: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This tip feels disconnected from the previous paragraph and the section overall. What was your intention behind it?
- [Version a Cluster Profile](../profiles/cluster-profiles/modify-cluster-profiles/version-cluster-profile.md) | ||
|
||
|
||
We also recommend you check out [Deploy Cluster Profile Updates](../clusters/cluster-management/update-k8s-cluster.md) tutorial to learn how to update your cluster profile. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also recommend you check out the Deploy Cluster Profile Updates tutorial to learn how to update your cluster profile.
@@ -34,6 +34,17 @@ We also offer Palette eXtended Kubernetes Edge (PXK-E) for Edge deployments. Ref | |||
|
|||
::: | |||
|
|||
### PXK and Palette VerteX | |||
|
|||
The PXK used in [Palette VerteX](../vertex/vertex.md) is compiled and linked with our [NIST-certified FIPS crypto module](../compliance.md#fips-140-2). PXK is by default enabled with [Ubuntu Pro](https://ubuntu.com/pro) with FIPS mode enabled. Additionally, the Operating System (OS) is hardened based on the NIST-800 standard. However, if you use a different OS through the [BYOOS](./byoos.md) pack, then you are responsible for ensuring FIPS compliance and hardening of the OS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With spelling out Operating System – do we expect that people who read this doc won't know what OS stands for?
* docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review Co-authored-by: Adelina Simion <[email protected]> * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]> (cherry picked from commit 51aaad2) Co-authored-by: Karl Cardenas <[email protected]>
* docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review Co-authored-by: Adelina Simion <[email protected]> * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]>
* docs: Clarify Kubernetes Support Lifecycle (#2013) DOC-1018 * docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review Co-authored-by: Adelina Simion <[email protected]> * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]> * docs: fixed merge conflicts * Optimised images with calibre/image-actions --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]>
* docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review Co-authored-by: Adelina Simion <[email protected]> * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]>
* docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review Co-authored-by: Adelina Simion <[email protected]> * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]>
* docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]>
* docs: k8s lifecycle DOC-1018 * docs: additional content * docs: updated content * docs: vale feedback * Optimised images with calibre/image-actions * docs: added version statement to k8s distros * docs: added statements about Palette VerteX * Apply suggestions from code review * docs: save * docs: feedback --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Adelina Simion <[email protected]>
🎉 This PR is included in version 4.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 4.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Describe the Change
This PR adds information about our support life cycle for Kubernetes.
Review Changes
💻 Preview URL
🎫 DOC-1014