Skip to content
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

Merge our work from OS Week to main #234

Merged
merged 11 commits into from
Aug 30, 2023
Merged

Merge our work from OS Week to main #234

merged 11 commits into from
Aug 30, 2023

Conversation

jfaltermeier
Copy link
Contributor

@jfaltermeier jfaltermeier commented Aug 30, 2023

  • all changes are stable enough to go to main
    • status for CRs to detect crash loops and display more information to user
    • validation for CRs
    • smaller stability fixes

Tickets:
#210
#200
#216
#205

jfaltermeier and others added 11 commits August 30, 2023 10:03
* extend our watchers to remember when they were last used
* add configurable timeout value where we stop the operator when
watchers appear stuck
* previous implementation was with ever increasing waiting times
* instead use a 4 step approach that increases waiting times at lower
pace
NOTE: Status handling for app definitions is commented out as there are still some issues

- Catch all exceptions when adding session, workspace, appdefinition resources and add error state
- Extend the resource clients for app definitions, sessions, and
workspaces to be able to handle the status subresource.
- Add basic status for our CRDs to track handling state of the operator
- Prevent crashloops by never handling resources that are in error or
handling state. The latter indicates an unexcepted crash during handling
(e.g. NPE).
- NOTE: The previous step was only dony for LAZY handlers. EAGER handlers did not change
- Exemplary sub steps for volume claim an attachment for workspace resources
- Increase resource versions for all CRs
- Move API, KIND, and CRD_NAME constants from Spec to resource classes
(e.g. from SessionSpec to Session) because they belong to the resource
itself. This became apparent when adding the Status to the resources

Part of #200
* added configurable handling to watchers
Enable checking and storing of AppDefinitions' handling in the operator
When handling of a resource is unexpectedly interrupted without throwing
an error, it currently remains in HANDLING state and is never handled
again. This could happen if the operator is shut down mid handling, e.g.
because of resource constraints.

This commit sets the resource to ERROR state and adds a message that
handling was unexpectedly interrupted before.

Contributed on behalf of STMicroelectronics

Signed-off-by: Lucas Koehler <[email protected]>
@jfaltermeier jfaltermeier merged commit baddf53 into main Aug 30, 2023
@jfaltermeier jfaltermeier deleted the osweek23 branch August 30, 2023 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants