-
Improvement
-
Resolution: Won't Do
-
Minor
-
None
This is a request to expose the existing defaultContainer option (as pointed below) to the Cloud configuration, in the Kubernetes Template side.
agent {
kubernetes {
defaultContainer 'maven'
yamlFile 'KubernetesPod.yaml'
}
}
This is how the new UI would be expected to be:
- is related to
-
JENKINS-41109 Kubernetes plugin defaults to wrong container
-
- Resolved
-
-
-
- Closed
-
- links to
[JENKINS-64778] Default container selector for the template configuration in the UI
Here is a workaround for your reference
Jack
added a comment - - edited Here is a workaround for your reference
https://github.com/zhan9san/init-jnlp All comments
Hi felipecassiors, we are no longer actively maintaining this plugin. However, if you find it useful and want to add the suggested functionality, feel free to send a Pull Request for it.
Thanks!
I do not think this is possible to implement. In order to use a nondefault container, the container step must be called. In Declarative Pipeline, that is normally done by using agent kubernetes. If you just use agent label (or run a non-Pipeline build), the kubernetes plugin is not even consulted.
Well, currently `jnlp` seems to be hardcoded as the default container. The same way `jnlp` is used if none is specified, this option should provide the user the ability to select the default container rather than using `jnlp`.
That is not possible. Using the jnlp container is qualitatively different from using other containers via the container step.
Here is a workaround for your reference
Jack
added a comment - - edited Here is a workaround for your reference
https://github.com/zhan9san/init-jnlp
This seems to be the only way to choose what container to use: being the jnlp container.
The drawback is that now I have an overloaded container with the Docker Daemon running in parallel with the JNLP service.