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
Describe the solution you'd like
A host might, for any reason, become unhealthy, with for example hardware issue or any other problem, while still running the agent. In this case, as a user, I would like a feature allowing me to flag that the ByoHost is temporarily unhealthy and should not be selected by BYOH to deploy a machine, even if the labels match, until I have fixed the issue and removed the flag.
This could be achieved using an unhealthy label on the ByoHost. When present, BYOH would not consider that ByoHost when selecting it.
The text was updated successfully, but these errors were encountered:
Hi @maelk, Thanks for trying out BYOH and raising this issue. We would like to capture more such use cases to improve the host selection logic. Could you elaborate a bit on what you mean by a node is unhealthy but the agent is still running? Is it possible for the agent to detect this unhealthy state so it can be handled in the code?
cc: @shivi28@Madhur97
Describe the solution you'd like
A host might, for any reason, become unhealthy, with for example hardware issue or any other problem, while still running the agent. In this case, as a user, I would like a feature allowing me to flag that the ByoHost is temporarily unhealthy and should not be selected by BYOH to deploy a machine, even if the labels match, until I have fixed the issue and removed the flag.
This could be achieved using an unhealthy label on the ByoHost. When present, BYOH would not consider that ByoHost when selecting it.
The text was updated successfully, but these errors were encountered: