You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Condition check for appwrappers with regards to quota. Currently Instascale doesn't seem to clarify the quota.
Description of Problem the Feature Should Solve
Currently Instascale looks for the appwrapper to be in "enqueued" state, and attempts to scale up. This will be handled correctly if the appwrapper is enqueued due to insufficient resources. However, if there are insufficient quota, instascale will fail to scale, without providing feedback for the reason.
Insufficient quota - Would not scale up - return information to user
Insufficient resources - Scale up.
The status of an appwrapper is provided as follows:
Status:
Conditions:
Last Transition Micro Time: 2023-08-30T10:12:09.846096Z
Last Update Micro Time: 2023-08-30T10:12:09.846096Z
Status: True
Type: Init
Last Transition Micro Time: 2023-08-30T10:12:09.905764Z
Last Update Micro Time: 2023-08-30T10:12:09.905764Z
Reason: AwaitingHeadOfLine
Status: True
Type: Queueing
Last Transition Micro Time: 2023-08-30T10:12:09.964831Z
Last Update Micro Time: 2023-08-30T10:12:09.964831Z
Reason: FrontOfQueue.
Status: True
Type: HeadOfLine
Last Transition Micro Time: 2023-08-30T10:12:09.995297Z
Last Update Micro Time: 2023-08-30T10:12:09.995297Z
Message: Insufficient resources to dispatch AppWrapper.
Reason: AppWrapperNotRunnable.
Status: True
Type: Backoff
Controllerfirsttimestamp: 2023-08-30T10:12:09.846096Z
Filterignore: true
Queuejobstate: Backoff
Sender: before [backoff] - Rejoining
State: Pending
When in the Pending state (Which is read as enqueued by instascale) the message can be:
"Insufficient quota to dispatch AppWrapper."
" Insufficient resources to dispatch AppWrapper."
The text was updated successfully, but these errors were encountered:
Name of Feature or Improvement
Condition check for appwrappers with regards to quota. Currently Instascale doesn't seem to clarify the quota.
Description of Problem the Feature Should Solve
Currently Instascale looks for the appwrapper to be in "enqueued" state, and attempts to scale up. This will be handled correctly if the appwrapper is enqueued due to insufficient resources. However, if there are insufficient quota, instascale will fail to scale, without providing feedback for the reason.
Insufficient quota - Would not scale up - return information to user
Insufficient resources - Scale up.
The status of an appwrapper is provided as follows:
When in the Pending state (Which is read as enqueued by instascale) the message can be:
The text was updated successfully, but these errors were encountered: