If we use a global pod (defined within the configure Jenkins panel).
The pod will end up in a «Error» state with the jnlp in error and the others container within still running.
So this easy example:
Where «slave-go» is a pod with 2 containers, a go container and a jnlp container.
The job will run with a success state, but the pod will fall in a Error state.
The log of the jnlp container seem to properly end:
But will immediately try to reconnect:
It will try all the protocols and than fail.
This is where is it interesting. If we use a podTemplate defintion, instead of a global pod definition. We will end up with a job running with sucess and a slave pod going to the proper «terminating» state.
So this example will work:
Please fix it, so that slave provided by a standard global pod definition end up in the proper state.
This was properly working with version 0.10 of the kubernetes plugin.