clean up references of cluster auto pause #4331
Conversation
christinaausley
added
kind/bug
There was a problem hiding this comment.
I should have caught this in the last PR; what is the status of autopause as a feature? It looks like it's in the alpha5 release notes, and available in production. Is the limitation captured in these warnings something we should have removed with 8.5 (or in 8.6)?
Depending on the answer I think we may be able to make the auto-pause warnings a bit clearer.
CC @ultraschuppi do you have any comments here? |
|
@christinaausley I can probably assist here, but might not be able to look at today - I will take a look tomorrow and should be able to clear up any confusion etc 👍 |
| :::caution | ||
| **Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. | ||
| ::: | ||
|
|
There was a problem hiding this comment.
Shouldn't this caution be deleted as auto-pause is out now?
| Free Trial `dev` (or untagged) clusters are automatically paused eight hours after a cluster is created or resumed from a paused state. Auto-pause occurs regardless of cluster usage. | ||
|
|
||
| You can resume a paused cluster at any time, which typically takes five to ten minutes to complete. See [resume your cluster](/components/console/manage-clusters/manage-cluster.md#resume-a-cluster). | ||
|
|
||
| - Clusters tagged as `test`, `stage`, or `prod` do not auto-pause. | ||
| - Paused clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. | ||
| - No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. | ||
| - When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. |
There was a problem hiding this comment.
| - When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. | |
| - Paused clusters still retain some functionality. For example, you can still execute BPMN timers and BPMN message catch events. |
Rewording suggestion
| :::caution | ||
| **Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. | ||
| ::: | ||
|
|
There was a problem hiding this comment.
See previous comment - remove?
| Free Trial `dev` (or untagged) clusters are automatically paused eight hours after a cluster is created or resumed from a paused state. Auto-pause occurs regardless of cluster usage. | ||
|
|
||
| You can resume a paused cluster at any time, which typically takes five to ten minutes to complete. See [resume your cluster](/components/console/manage-clusters/manage-cluster.md#resume-a-cluster). | ||
|
|
||
| - Clusters tagged as `test`, `stage`, or `prod` do not auto-pause. | ||
| - Paused clusters are automatically deleted after 30 consecutive paused days. You can change the tag to avoid cluster deletion. | ||
| - No data is lost while a cluster is paused. All execution and configuration is saved, but cluster components such as Zeebe and Operate are temporarily disabled until you resume the cluster. | ||
| - When a cluster is paused, not all functionality is limited. For example, you may still execute BPMN timers and BPMN message catch events. |
There was a problem hiding this comment.
See previous rewording suggestion
|
@mesellings Given the changes over the past few weeks with auto-pause, I'm just going to close this out 👍 Thank you for your review! |
|
Sounds good thank you! 👍 |
Description
Closes https://github.com/camunda/developer-experience/issues/390.
When should this change go live?
holdlabel or convert to draft PR)PR Checklist
/versioned_docsdirectory./docsdirectory (aka/next/).