You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As pointed out in #598 (comment), certain config changes are difficult to propagate to DevWorkspaceRoutings (and thus, to the objects that the routing reconciler manages). This is because once services/ingresses/routes are created, there aren't many events on the cluster that trigger new reconciles. Since we do no cleanup when a workspace is stopped, even restarting a workspace may not trigger any reconciles in the routing controller.
One way to work around this would be to propagate the workspaces .spec.started field to the created DevWorkspaceRouting, which would at least trigger reconciles when a workspace is restarted.
The text was updated successfully, but these errors were encountered:
Description
As pointed out in #598 (comment), certain config changes are difficult to propagate to DevWorkspaceRoutings (and thus, to the objects that the routing reconciler manages). This is because once services/ingresses/routes are created, there aren't many events on the cluster that trigger new reconciles. Since we do no cleanup when a workspace is stopped, even restarting a workspace may not trigger any reconciles in the routing controller.
One way to work around this would be to propagate the workspaces
.spec.started
field to the created DevWorkspaceRouting, which would at least trigger reconciles when a workspace is restarted.The text was updated successfully, but these errors were encountered: