feat!: introducing sleeping status #773
Merged
+11
−7
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.
Kamaji already offers a scale-to-zero feature, which had some bugs prior to #771.
A TenantControlPlane, although scaled to zer,o was always marked as
Ready
even tho this was inaccurate, bringing some errors when scaling back to a positive amount of replicas, and logging false positive errors since the API Server wasn't yet ready from the Soot manager due to new pods being rolled out.This PR introduces the new status enum
Sleeping
, useful to inform operators if a Tenant Control Plane is scaled to zero.Marking the commit as important since a Custom Resource Definition update must be applied.