Closed VanillaSpoon closed 11 months ago
Hey @asm582 I just pushed some changes there regarding the conditions message :)
Thanks @VanillaSpoon for the quick turnaround, Can you please add some screenshots of manual tests performed on this PR please?
Hi @asm582 I have added screenshots and an explanation of the scale-up testing to the pr description :)
Thanks @VanillaSpoon
LGTM
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: asm582
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Issue link
Closes: https://issues.redhat.com/browse/RHOAIENG-861
What changes have been made
This pr contains an update to ensure the AW is in a pending state, with a condition of Insufficient resources before scaling up the specified resources for the appwrapper. This ensure resource usage efficiency for the cluster.
Verification steps
Steps I have followed to ensure the functionality. On a cluster with 2 m6i.2xlarge worker nodes.
I provisioned an appwrapper which required more resources than available on the cluster.
This ensured the aw would reach pending state with the condition on Insufficient resources, inducing a scale up of the specified resources, as can be seen here:
I also provisioned an appwrapper with required resources within the clusters available
With this the appwrapper was dispatched without the need for scaling up. As can be seen in the following:
Checks