Fix #172 - Introduce Flow Durable Kubernetes module#188
Open
ricardozanini wants to merge 15 commits intoquarkiverse:mainfrom
Open
Fix #172 - Introduce Flow Durable Kubernetes module#188ricardozanini wants to merge 15 commits intoquarkiverse:mainfrom
ricardozanini wants to merge 15 commits intoquarkiverse:mainfrom
Conversation
|
🚀 PR Preview 740ee7d has been successfully built and deployed to https://quarkiverse-flow-pr-188-preview.surge.sh
|
ricardozanini
force-pushed
the
issue-172
branch
2 times, most recently
from
2c1dbc2 to
893bca0
Compare
ricardozanini
force-pushed
the
issue-172
branch
2 times, most recently
from
0414843 to
b8c1b37
Compare
ricardozanini
force-pushed
the
issue-172
branch
from
b8c1b37 to
9579bbb
Compare
Member
Author
Member
Author
|
@quarkiverse/quarkiverse-flow-triage team I'm waiting for reviews :) |
mcruzdev
reviewed
Feb 27, 2026
durable-kubernetes/runtime/src/main/java/io/quarkiverse/flow/durable/kube/PoolController.java
Show resolved
Hide resolved
mcruzdev
reviewed
Feb 27, 2026
durable-kubernetes/runtime/src/main/java/io/quarkiverse/flow/durable/kube/PoolController.java
Outdated
Show resolved
Hide resolved
mcruzdev
reviewed
Feb 27, 2026
mcruzdev
reviewed
Feb 27, 2026
mcruzdev
approved these changes
Feb 27, 2026
Member
mcruzdev
left a comment
mcruzdev
left a comment
There was a problem hiding this comment.
It looks great @ricardozanini.
I left a few comments!
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
ricardozanini
force-pushed
the
issue-172
branch
from
bf6dfff to
f06388b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #172
In this PR:
Introduce a new
durable-kubernetesmodule responsible to coordinate Lease objects in-cluster to guarantee safe Workflow Application IDs across pod restarts, disruption, drain, etc. This is REQUIRED for use case persistence for the Quarkus Flow application deployed on Kubernetes.Reviewers, please check the documentation and example to understand more in-depth the concepts behind it before checking the code.
This module introduces the operator pattern to Quarkus Flow. We are not building a whole custom Kubernetes operator for the project just yet. This requirement is simple enough and doesn't add a large footprint to the user's application; it's just a small scheduler querying a cached k8s API resource.