[FLINK-38577] Added BlueGreen active deployment ingress #1049
Merged
gyfora merged 2 commits intoapache:mainfrom Feb 2, 2026
Merged
[FLINK-38577] Added BlueGreen active deployment ingress #1049gyfora merged 2 commits intoapache:mainfrom
gyfora merged 2 commits intoapache:mainfrom
Conversation
gyfora
reviewed
Jan 27, 2026
...rator/src/main/java/org/apache/flink/kubernetes/operator/utils/bluegreen/BlueGreenUtils.java
Show resolved
Hide resolved
gyfora
reviewed
Jan 27, 2026
...va/org/apache/flink/kubernetes/operator/controller/bluegreen/BlueGreenDeploymentService.java
Outdated
Show resolved
Hide resolved
gyfora
approved these changes
Jan 30, 2026
Contributor
|
please rebase on the latest main, then we can merge this |
kengtin
approved these changes
Jan 30, 2026
…c + resolve path conflict on Blue and Green deployment ingresses
…tries with exponential backoff
60168a4 to
cc322e8
Compare
Contributor
Author
|
Resolved conflicts |
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
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.
[FLINK-38577] FlinkBlueGreenDeployment Stable Ingress
What is the purpose of the change
Adds parent-level ingress support to FlinkBlueGreenDeployment, enabling users to specify ingress configuration at the BlueGreen deployment level rather than only at the child FlinkDeployment level. The ingress automatically switches between Blue and Green deployments during transitions and can be updated independently without triggering a full blue-green transition.
Brief change log
Added ingress field to FlinkBlueGreenDeploymentSpec API
Modified Blue and Green deployments ingress names and routes to be preappended with Blue|Green
Implemented reconcileBlueGreenIngress() in IngressUtils for BlueGreen-specific ingress management
Added ingress secondary resource registration in FlinkBlueGreenDeploymentController.prepareEventSources()
Implemented reconcileIngressForActiveDeployment() in BlueGreenDeploymentService for immediate ingress updates in ACTIVE states
Updated ActiveStateHandler to reconcile ingress during normal reconciliation loops
Added exception handling around ingress reconciliation during finalization
Refactored IngressUtils.getIngress() to accept IngressSpec instead of FlinkDeploymentSpec for code reuse
Updated CRD schema to include ingress specification
Verifying this change
This change added tests and can be verified as follows:
Unit Tests:
E2E Test:
Also tested on remote K8s cluster with the following scenarios:
Does this pull request potentially affect one of the following parts:
Documentation