Skip to content

Commit

Permalink
docs: DOC-1150 deprecated packs clarification (#2682) (#2823)
Browse files Browse the repository at this point in the history
* docs: DOC-1150

* chore: final touches

* Apply suggestions from code review



* chore: prettier

---------

Co-authored-by: caroldelwing <carolina.delwing@spectrocloud.com>
  • Loading branch information
karl-cardenas-coding and caroldelwing committed May 13, 2024
1 parent 239f68c commit 63f82bf
Show file tree
Hide file tree
Showing 2 changed files with 22,712 additions and 11,915 deletions.
16 changes: 11 additions & 5 deletions docs/docs-content/integrations/maintenance-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,8 @@ We provide Cloud Native Computing Foundation (CNCF) Kubernetes updates as follow
| **Minor** | Provided within eight weeks of a new Kubernetes release. |
| **Patch** | Provided within four weeks of a new Kubernetes release. |

You can learn about our Kubernetes support lifecycle in the [Kubernetes Support Lifecycle](kubernetes-support.md) page.

### CNI Packs

We provide CNI pack updates as follows:
Expand Down Expand Up @@ -111,18 +113,22 @@ We adhere to the following stages of deprecation:

- **Deprecated**: When a pack or a pack version is deprecated, this indicates it will be removed in the future. You will
still be able to create new cluster profiles using the pack and launch clusters using existing profiles that contain
the pack.
the pack. Active and deployed clusters are not affected as the pack is still available in Palette.

The pack remains in _Deprecated_ state for three months before it moves to _Disabled_ state.

- **Disabled**: When a pack is disabled, it is no longer available for selection in Palette. When creating new profiles,
you must use a newer version of the pack. You can still launch clusters using existing profiles that contain the
disabled pack.
you must use a newer version of the pack. You can still launch new clusters using existing profiles that contain the
disabled pack. Active and deployed clusters are not affected as the pack is still available in Palette.

The pack remains in _Disabled_ state for three months before it is deleted.

- **Deleted**: When a pack is deleted, it is removed from Palette. An active cluster that contains the deleted pack will
continue to operate. However, you will not be able to deploy a new cluster profile that contains the deleted pack.
- **Deleted**: When a pack is deleted, it is removed from Palette. You will not be able to deploy a new cluster with a
cluster profile containing the deleted pack or create a new cluster profile referencing the deleted pack. We recommend
that you update your existing cluster profiles to use a newer version of the pack and apply the changes to your active
clusters. Active clusters using the deleted pack will typically not experience issues if a node is rebooted or if a
new node is added to the cluster. However, if there are any problems with the deleted pack version, such as upstream
bugs, you may encounter issues if they affect scaling or other cluster operations.

:::info

Expand Down
Loading

0 comments on commit 63f82bf

Please sign in to comment.