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

Continue resource handling after being cancelled before #221

Open
lucas-koehler opened this issue Aug 2, 2023 · 3 comments
Open

Continue resource handling after being cancelled before #221

lucas-koehler opened this issue Aug 2, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request prio-medium

Comments

@lucas-koehler
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Follow up of #200.

When the operator starts handling a CR (i.e. AppDefinition, Session, Workspace), it marks the resource as HANDLING. If the operator is killed (e.g. by Kubernetes due to resources or an update), the resource is never set to HANDLED.
Currently, resources in HANDLING are never processed again to prevent handling resources that caused unexpected crashes,
However, unexpected crashes can be caught (and should already after #200).

Describe the solution you'd like

When a resource with status HANDLING is processed again, the operator needs to consider that encountering an already completed step does not mean that handling was finished. Instead, the operator should only execute the missing steps.

Describe alternatives you've considered

None, eventually we need to be safe against operators being stopped while handling a resource.

Cluster provider

No response

Additional information

No response

@lucas-koehler lucas-koehler added the enhancement New feature or request label Aug 2, 2023
@lucas-koehler lucas-koehler changed the title Continue resource handling when it was cancelled unexpectedly before Continue resource handling after being cancelled before Aug 2, 2023
@jfaltermeier jfaltermeier added this to the OS Week 23 milestone Aug 2, 2023
@jfaltermeier jfaltermeier moved this to Todo in OS Week 23 Aug 2, 2023
@jfaltermeier jfaltermeier moved this from Todo to In Progress in OS Week 23 Aug 18, 2023
@lucas-koehler lucas-koehler self-assigned this Aug 30, 2023
lucas-koehler added a commit that referenced this issue Aug 31, 2023
Adds support to the operator to handle AppDefinitions that are in
HANDLING state. This happens when the operator was unexpectedly shut
down while handling the AppDefinition before.

No logic changes in creating Kubernetes resources are necessary because
the handling was already idempotent.

Contributed on behalf of STMicroelectronics
lucas-koehler added a commit that referenced this issue Aug 31, 2023
The Workspace handling already makes sure steps are not executed twice.
Thus, we can simply try handling again

Contributed on behalf of STMicroelectronics
Copy link

This issue is stale because it has been open for 180 days with no activity.

@github-actions github-actions bot added the stale label Feb 27, 2024
@jfaltermeier
Copy link
Contributor

Keep open

@github-actions github-actions bot removed the stale label Feb 28, 2024
Copy link

This issue is stale because it has been open for 180 days with no activity.

@github-actions github-actions bot added the stale label Aug 27, 2024
@jfaltermeier jfaltermeier removed this from the OS Week 23 milestone Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request prio-medium
Projects
None yet
Development

No branches or pull requests

2 participants