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
For context, we currently deploy our Vela workers with autoscaling configuration enabled so this means our workers will periodically scale up and down throughout the day based off the activity and build volume for our installation. However, this unfortunately leads to some challenges when attempting to leverage the new workers page introduced in the 0.24 release of Vela because the data can become inaccurate and out-of-sync very quickly. We're looking to update the workers page for our installation so it better reflects current state and get closer to near real-time information on it:
There are two main pieces we're looking to update on this page for each record in the workers table:
the active field being set to false to denote that the worker is no longer active and never will be
the status field being set to something to denote that the worker is no longer active and never will be
As we were exploring the current enum list available for the status field, we felt there wasn't an ideal one to pick from:
To better state that in words, given the current list I linked above our options are:
available
busy
idle
error
From our perspective, it seems confusing to have a worker in an idle status that has active as false (no in UI). We'd like to request that a new status be added that we could update workers to and some initial ideas we had were:
decommissioned
offline
shutdown
Value
enable admins of Vela installations to better reflect the status of workers that will never be available/idle again
Definition of Done
a new enum has been added to the list of worker statuses that reflects a worker is offline
Effort (Optional)
unsure at this time
Impacted Personas (Optional)
admins of a Vela installation
The text was updated successfully, but these errors were encountered:
Description
For context, we currently deploy our Vela workers with autoscaling configuration enabled so this means our workers will periodically scale up and down throughout the day based off the activity and build volume for our installation. However, this unfortunately leads to some challenges when attempting to leverage the new
workers
page introduced in the0.24
release of Vela because the data can become inaccurate and out-of-sync very quickly. We're looking to update theworkers
page for our installation so it better reflects current state and get closer to near real-time information on it:There are two main pieces we're looking to update on this page for each record in the
workers
table:active
field being set tofalse
to denote that the worker is no longer active and never will bestatus
field being set to something to denote that the worker is no longer active and never will beAs we were exploring the current enum list available for the
status
field, we felt there wasn't an ideal one to pick from:https://github.com/go-vela/types/blob/v0.24.0/constants/worker_status.go
To better state that in words, given the current list I linked above our options are:
available
busy
idle
error
From our perspective, it seems confusing to have a worker in an
idle
status that hasactive
asfalse
(no
in UI). We'd like to request that a new status be added that we could update workers to and some initial ideas we had were:decommissioned
offline
shutdown
Value
workers
that will never beavailable
/idle
againDefinition of Done
Effort (Optional)
Impacted Personas (Optional)
The text was updated successfully, but these errors were encountered: