consolidate manage cluster section #4202
Conversation
christinaausley
added
component:docs
|
👋 🤖 🤔 Hello! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.5/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
| @@ -40,3 +40,7 @@ Users without **Admin** roles can deploy only on `dev`, `test`, or `stage` clust | |||
|  | |||
|
|
|||
| 3. After the cluster is created, click on the cluster name to visit the cluster detail page. | |||
|
|
|||
| :::note | |||
| **Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality will be limited, including the execution of BPMN timers and BPMN message catch events. To resume your cluster, navigate to the **Clusters** tab in Console, select the cluster name, and click **Resume cluster** within the **Cluster Details**. | |||
There was a problem hiding this comment.
When a cluster is paused, not all functionality will be limited, including the execution of BPMN timers and BPMN message catch events.
not sure what this means, times will continue to work? ;)
Development clusters will be paused if they go unused for two hours
i don't think this is how it works
There was a problem hiding this comment.
I just migrated over the existing content for this PR -- is the content outdated then? Do you know the timeframe of when clusters are paused?
There was a problem hiding this comment.
@ultraschuppi Do you have any insight here I can update accordingly?
There was a problem hiding this comment.
the current state of autopausing:
- clusters in trial organisations
- tagged with dev
- will be sent to sleep ~ 8h after they have been created / woken up the last time
we put trial-org clusters to sleep after a few days if we think they are not used (no process instances started), but i don't think this is even communicated
To resolve in a separate PR 👍
There was a problem hiding this comment.
Also
When a cluster is paused, not all functionality will be limited, including the execution of BPMN timers and BPMN message catch events.
not sure what this means, times will continue to work? ;)
I've updated this wording @ultraschuppi 👍
|
I'm going to resolve the conflicts here and backport, with plans to open a PR regarding https://github.com/camunda/developer-experience/issues/390 this week. |
|
This is ready for final review if you don't mind having a second look @conceptualshark 😄 |
|
🧹 Preview environment for this PR has been torn down. |
|
@christinaausley I see this work was merged (looks good btw!), unfortunately this puts the Resume cluster: At the bottom of the https://docs.camunda.io/docs/next/components/concepts/clusters/ page How shall we handle this? Shall I create an issue and PR and take it out, or are you working on the cluster docs for any other issues atm? |
|
@mesellings Feel free to remove this as you see fit based on your ongoing work 👍 Apologies for the overlap. |
|
Np - will do thanks! 👍 |
|
Issue created to address this: #4373 |
Description
Closes https://github.com/camunda/developer-experience/issues/241 by consolidating cluster actions into one page.
Notes
Will backport upon approval.
NOTE -- this PR is solely within the scope of https://github.com/camunda/developer-experience/issues/241, and does not address #3199.
This PR only condenses the cluster actions into one page as a starting point.
Tomorrow, I will launch a Miro board to discuss the content and sidebar layout in full that comes with #3199. CC @theburi
When should this change go live?
holdlabel or convert to draft PR)PR Checklist
/versioned_docsdirectory./docsdirectory (aka/next/).