Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43235

Total container cap of 10 reached when NO slaves are running?

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • kubernetes-plugin
    • None

      I have currently 39 pods running in the cluster default namespace. None of them are created by jenkins.plugins.kubernetes.

      If i increase limit to for example 50 it starts to create slaves. But why does it count more than i should? 

      Mar 30, 2017 4:54:50 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave
INFO: Total container cap of 10 reached, not provisioning: 20 running in namespace default
Mar 30, 2017 4:55:00 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Excess workload after pending Spot instances: 1
Mar 30, 2017 4:55:00 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave
INFO: Total container cap of 10 reached, not provisioning: 20 running in namespace default
Mar 30, 2017 4:55:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Excess workload after pending Spot instances: 1
Mar 30, 2017 4:55:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave
INFO: Total container cap of 10 reached, not provisioning: 20 running in namespace default
Mar 30, 2017 4:55:20 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
INFO: Excess workload after pending Spot instances: 1
Mar 30, 2017 4:55:20 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave

      running a new installatin of jenkins 2.46.1 and kubernetes plugin 0.11

            csanchez Carlos Sanchez
            jonaz Jonas Falck
            Votes:
            2 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: