You're right, the api only seems to define container limits. While I still look for how the api infers these; I can usually define them in a yaml like this <https://gist.github.com/JaveriaK/cfdca36151ee06a6da55c8db073718c7#file-limits-yaml-L14> with a "type: Pod" label, and it puts limits on my namespace for both PODs and containers:
<https://lh3.googleusercontent.com/-9dWzKH4aTJ0/WIpG6wuKnXI/AAAAAAAABmg/ES2kASMqwPkL7hDGoD1lqqqK1l1PlR0FACLcB/s1600/Screen%2BShot%2B2017-01-26%2Bat%2B11.00.08%2BAM.png> However I was able to successfully run a build and create PODs in a namespace without any set limits. Setting the container name to 'jnlp' seems to not let it work anywhere though with obscure errors (I couldn't make out anything from these..): Jan 26, 2017 6:29:38 PM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision > > INFO: Excess workload after pending Spot instances: 1 > > Jan 26, 2017 6:29:38 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl >> apply > > INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 >> executors. Remaining excess workload: 0 > > Jan 26, 2017 6:29:38 PM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback >> call > > INFO: Created Pod: jenkins-slave-e6720c6adbb4 > > Jan 26, 2017 6:29:38 PM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback >> call > > INFO: Waiting for Pod to be scheduled (0/100): jenkins-slave-e6720c6adbb4 > > Jan 26, 2017 6:29:44 PM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback >> call > > SEVERE: Error in provisioning; slave=KubernetesSlave name: >> jenkins-slave-e6720c6adbb4, >> template=org.csanchez.jenkins.plugins.kubernetes.PodTemplate@67f9564d > > java.lang.IllegalStateException: Containers are terminated with exit >> codes: {jnlp=0} > > at >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:600) > > at >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:532) > > at >> jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > at java.lang.Thread.run(Thread.java:745) > > Jan 26, 2017 6:29:48 PM hudson.slaves.NodeProvisioner$2 run > > WARNING: Provisioned agent Kubernetes Pod Template failed to launch > > java.lang.IllegalStateException: Containers are terminated with exit >> codes: {jnlp=0} > > at >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:600) > > at >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback.call(KubernetesCloud.java:532) > > at >> jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > at java.lang.Thread.run(Thread.java:745) > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/991159ab-4712-4d9f-afe0-c07cf88d2f82%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
