THREESCALE-14267 Add 3 status conditions; Use new status for requeue#1155
Open
urbanikb wants to merge 3 commits into3scale:masterfrom
Open
THREESCALE-14267 Add 3 status conditions; Use new status for requeue#1155urbanikb wants to merge 3 commits into3scale:masterfrom
urbanikb wants to merge 3 commits into3scale:masterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #1155 +/- ##
==========================================
+ Coverage 39.34% 42.57% +3.22%
==========================================
Files 205 202 -3
Lines 23363 20568 -2795
==========================================
- Hits 9193 8757 -436
+ Misses 13184 11030 -2154
+ Partials 986 781 -205
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
e9384ab to
a1878ac
Compare
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
a1878ac to
6313195
Compare
…erface Replace direct calls to unexported functions (calculateStatus, deploymentsAvailableCondition, routesReadyCondition, watchedSecretsExist, secretsAvailableCondition) with a single table-driven test that exercises the public Reconcile() method end-to-end. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
6313195 to
d3d0f96
Compare
- fix config map fixture that incorrectly assumed operator namespace will always match WATCH_NAMESPACE var - fix error checking in preflight status reconciliation when NotFound error was not detected correctly and would always crash instead
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.
Fix:
What
Previously, APIManager exposed a single Available condition that collapsed three independent system checks into one opaque signal. When
Available=Falsethere was no way to tell from the CR alone whether the problem was with deployments, routes, or secrets.New conditions
Three independent sub-conditions are now present in
.status.conditions:DeploymentsAvailableRoutesReadySecretsAvailableAvailable remains a roll-up: True if all above sub-conditions are True.
Change in status reporting
Before: On a broken install you would see:
After: The root cause is visible without inspecting cluster resources:
Backwards compatibility
The Available condition continues to surface Reason and Message from SecretsAvailable when secrets are missing, preserving existing automation that reads those fields from Available.
Verification
Tested that the status behaves as expected (namespace
3scale-abcbelow).Also verified that if a different version of operator (earlier 2.16 from public bundle) is installed in a different namespace (namespace
3scale-parallel), it will be able to set status on the CR in that namespace.