We may use additional fields in the custom resources metadata to save the current step the operator way making and number of tries for this step.
If the operator sees that there were already multiple tries to read the container image from an app definition, it may assume that this will fail and skip over it.
Is your feature request related to a problem? Please describe.
The operator should be able to detect crash loops and skip over problematic custom resources.
Reproducer Session theia-cloud branch osweek23-1 theia-cloud-helm branch osweek23-1 terraform test-configuration 2-01_try-now
kubectl apply -f osweek23/empty-session.yaml
Reproducer Workspace theia-cloud branch osweek23-1 theia-cloud-helm branch osweek23-1 terraform test-configuration 2-01_try-now
kubectl apply -f osweek23/empty-workspace.yaml
Reproducer AppDefinition theia-cloud branch osweek23-2 theia-cloud-helm branch osweek23-1 terraform test-configuration 2-01_try-now
kubectl apply -f osweek23/coffee-session.yaml
Describe the solution you'd like
We may use additional fields in the custom resources metadata to save the current step the operator way making and number of tries for this step.
If the operator sees that there were already multiple tries to read the container image from an app definition, it may assume that this will fail and skip over it.
Describe alternatives you've considered
-
Cluster provider
No response
Additional information
No response