Bug-fix: Retry reconciliation on transient errors and stale LB state - #149
Open
jlamillan wants to merge 1 commit into
Open
Bug-fix: Retry reconciliation on transient errors and stale LB state#149jlamillan wants to merge 1 commit into
jlamillan wants to merge 1 commit into
Conversation
jlamillan
force-pushed
the
jlamillan/retry-transient-errors
branch
from
June 24, 2026 18:29
5d11258 to
d58fb67
Compare
jlamillan
force-pushed
the
jlamillan/retry-transient-errors
branch
from
June 24, 2026 23:25
d58fb67 to
81ee683
Compare
jlamillan
force-pushed
the
jlamillan/retry-transient-errors
branch
3 times, most recently
from
July 2, 2026 18:56
25a6b51 to
f9698f0
Compare
Signed-off-by: jesse.millan <jesse.millan@oracle.com>
jlamillan
force-pushed
the
jlamillan/retry-transient-errors
branch
from
July 29, 2026 18:43
f9698f0 to
cfc166e
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
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.
Summary
Harden OCI Native Ingress reconciliation against transient load balancer dependency errors, stale LB state, and IngressClass annotation writes.
Why
OCI load balancer updates do not become visible all at once. The controller can reconcile related resources before a newly created listener, backend set, updated ETag, or IngressClass annotation is visible. These are temporary convergence states, so the controller should keep retrying instead of treating them as final failures.
Manual verification
Verified with OCI Native Ingress CI failures where routing policy/backend reconciliation hit missing backend sets, missing route_443, stale ETags, and a missing LB ID annotation while the LB was still converging. Confirmed the controller now treats those dependency and stale-state paths as transient retries, refreshes LB state before subsequent backend update attempts, and verifies IngressClass annotation writes after patching.
I’ve repeatedly run our product's integration tests in OCI Native mode with this change which creates multiple OCI load balancers with DNS names and certificates across different Ingress configurations, then validates the endpoints end to end. I also reviewed the OCI Load Balancer work requests and OCI Native ingress controller logs during the CI tests. All checks look good with this change.