-
Notifications
You must be signed in to change notification settings - Fork 65
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
SpaceProvisionerConfig should only be ready when underlying ToolchainCluster is ready #1033
SpaceProvisionerConfig should only be ready when underlying ToolchainCluster is ready #1033
Conversation
when the referenced ToolchainCluster is ready. This should make sure we never provision to offline clusters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice Job 👍
I have only few questions related to the unit tests.
controllers/spaceprovisionerconfig/spaceprovisionerconfig_controller_test.go
Show resolved
Hide resolved
controllers/spaceprovisionerconfig/spaceprovisionerconfig_controller_test.go
Outdated
Show resolved
Hide resolved
controllers/spaceprovisionerconfig/spaceprovisionerconfig_controller_test.go
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
Thanks for addressing my comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great overall 👍 , just made a small suggestion
controllers/spaceprovisionerconfig/spaceprovisionerconfig_controller.go
Outdated
Show resolved
Hide resolved
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice 👍 🚀
we can add more validations long-term - eg. checking the threshold against the actual usage, so some of the capacity-management logic would be moved here. In this way, it would be visible directly in the status of the SPC if the cluster is available for provisioning or not and for what reason.
controllers/spaceprovisionerconfig/spaceprovisionerconfig_controller.go
Outdated
Show resolved
Hide resolved
…en-tc-ready # Conflicts: # go.mod # go.sum
…to spc-ready-only-when-tc-ready
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool, thanks for the additional changes 👍
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MatousJobanek, metlos, mfrancisc, rajivnathan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1033 +/- ##
==========================================
+ Coverage 84.72% 84.81% +0.08%
==========================================
Files 55 55
Lines 4909 4918 +9
==========================================
+ Hits 4159 4171 +12
+ Misses 577 573 -4
- Partials 173 174 +1
|
93dda62
into
codeready-toolchain:master
Fix the SpaceProvisionerConfig controller to only set the SPC ready when the referenced ToolchainCluster is ready. This should make sure we never provision to offline clusters.
Associated PRs: