Hi, thank you.

What I meant by 'Jenkins master is always available', that we have on-demand NodeGroup with permanent size of 1, one EC2 runs always with Jenkins master inside and every time you put something like jenkins.eks.you.domain.com to your browser you able to reach it immediately and there is no need to wait for instance to be provisioned first and Jenkins configured, like in spot Instance nodeGroup which of size 0(most of the time) and every time you need need to execute workflow you need to wait for new node to be provisioned first, then job executed, then we removing the the node and NodeGroup again of size 0.