-
Notifications
You must be signed in to change notification settings - Fork 172
docs: add warning for workspace restarts on automount changes (CRW-9859) #3025
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
Conversation
|
🎊 Navigate the preview: https://698ca955bbc046a8c8547bed--eclipse-che-docs-pr.netlify.app 🎊 |
|
|
||
| [WARNING] | ||
| ==== | ||
| Applying a Secret or ConfigMap with the `controller.devfile.io/mount-to-devworkspace: 'true'` label (or modifying an existing one) triggers an immediate restart of all running workspaces in that {namespace} by applying the configuration. Ensure users have saved their work before applying these changes. |
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.
| Applying a Secret or ConfigMap with the `controller.devfile.io/mount-to-devworkspace: 'true'` label (or modifying an existing one) triggers an immediate restart of all running workspaces in that {namespace} by applying the configuration. Ensure users have saved their work before applying these changes. | |
| Applying or modifying a `Secret` or `ConfigMap` with the `controller.devfile.io/mount-to-devworkspace: 'true'` label restarts all running workspaces in the namespace. Ensure that users save their work before you apply these changes. |
|
|
||
| [WARNING] | ||
| ==== | ||
| Applying a Secret or ConfigMap with the `controller.devfile.io/mount-to-devworkspace: 'true'` label (or modifying an existing one) triggers an immediate restart of all running workspaces in that {namespace} to apply the configuration. Ensure users have saved their work before applying these changes. |
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.
| Applying a Secret or ConfigMap with the `controller.devfile.io/mount-to-devworkspace: 'true'` label (or modifying an existing one) triggers an immediate restart of all running workspaces in that {namespace} to apply the configuration. Ensure users have saved their work before applying these changes. | |
| Applying or modifying a `Secret` or `ConfigMap` with the `controller.devfile.io/mount-to-devworkspace: 'true'` label restarts all running workspaces in the namespace. Ensure that users save their work before you apply these changes.. |
|
|
||
| [WARNING] | ||
| ==== | ||
| Applying a Secret or ConfigMap with the `controller.devfile.io/mount-to-devworkspace: 'true'` label (or modifying an existing one) triggers an immediate restart of all running workspaces in that {namespace} by applying the configuration. Ensure users have saved their work before applying these changes. |
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.
| Applying a Secret or ConfigMap with the `controller.devfile.io/mount-to-devworkspace: 'true'` label (or modifying an existing one) triggers an immediate restart of all running workspaces in that {namespace} by applying the configuration. Ensure users have saved their work before applying these changes. | |
| Applying or modifying a `Secret` or `ConfigMap` with the `controller.devfile.io/mount-to-devworkspace: 'true'` label restarts all running workspaces in the namespace. Ensure that users save their work before you apply these changes. |
Signed-off-by: Badre Tejado <btejado@redhat.com>
065899a to
98c5282
Compare
What does this pull request change?
This PR adds a WARNING block to the Secret and ConfigMap mounting procedures. It informs users and administrators that applying or modifying resources with the
controller.devfile.io/mount-to-devworkspace: 'true'label triggers an immediate restart of all running workspaces in the affected namespace to apply the configuration.What issues does this pull request fix or reference?
Referenced Jira: https://issues.redhat.com/browse/CRW-9859
Specify the version of the product this pull request applies to
Eclipse Che (Upstream)
Pull Request checklist