The Web Terminal Operator depends on the DevWorkspace Operator to provide the DevWorkspace and DevWorkspaceTemplate Custom Resource Definitions used to define terminal instances. When the WTO controller pod starts up, it attempts to create DevWorkspaceTemplates for the normal web terminal components.

However, when installing WTO requires also installing DWO (the usual case), the WTO controller gets created before the DWO (and corresponding CRDs) are installed on the cluster, causing the WTO controller to enter a crashloop until the CRDs are available and the DevWorkspace Operator is running.

While this does not interfere with WTO functionality, it results in confusing messages in the OperatorHub install progress page, where the operator switches between "installed" and "waiting for controller to become ready" multiple times.

To fix this, WTO should either check to see if CRDs are present (and wait if they are not) or have a retry mechanism (with timeout) before propagating the create error up and shutting down.