Follow-up to #4.
When a user already at the pod cap opens a connection that would spawn a new box, the config server denies the config POST and ContainerSSH fails closed with the generic Cannot authenticate at this time. The real reason is only visible in server logs.
Goal: surface a readable per-user reason (e.g. pod limit (3) reached — delete a box) if achievable without modifying ContainerSSH; otherwise document the behavior prominently in the chart README/NOTES.
Follow-up to #4.
When a user already at the pod cap opens a connection that would spawn a new box, the config server denies the config POST and ContainerSSH fails closed with the generic
Cannot authenticate at this time. The real reason is only visible in server logs.Goal: surface a readable per-user reason (e.g.
pod limit (3) reached — delete a box) if achievable without modifying ContainerSSH; otherwise document the behavior prominently in the chart README/NOTES.