The Concurrency Limit is not always respected.

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: kubernetes-plugin
    • None
    • Environment:
      Jenkins ver. 2.176.3
      Kubernets-plugin: 1.19.3
    • kubernetes 1.27.1

      I create a lot of jobs 300 of them using jobdsl.

      I have set the Kubernetes-plugin Concurrency Limit set to 20

      Then Kubernetes plugin spins up a new node/pod for almost every job. All but a few get in pending state due to resource limit in my Kubernetes cluster, the pending pods is removed after a while and then recreated.

      Sometimes the concurrency Limit is respected, i see a lot of this in my jenkins log. but it should never get to to 184 running or pending.

      INFO: Maximum number of concurrently running agent pods (20) reached for Kubernetes Cloud kubernetes, not provisioning: 184 running or pending in namespace jenkins with Kubernetes labels {jenkins=slave}
      
      

       

            Assignee:
            Vincent Latombe
            Reporter:
            Carl Dorbeus
            Votes:
            10 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated: