Hi Carlos
I have upgraded the plugin to the latest version 1.18.3 and we are still
hitting the same issue but with a slightly different error message.
Any chance that you can look into this?
Thanks,
Junaid
On Friday, December 14, 2018 at 1:08:55 PM UTC, Simon Young wrote:
>
> Unfortunately it
Unfortunately it's not fixed in 1.13.8. We now see this:
Connection was rejected, you should increase the Max connections to
Kubernetes API
I tried increasing Max connections to 400. The next build passed, but
subsequent builds are failing, just like we saw with 1.13.7.
I have to roll back to
This should be fixed in 1.13.8
On Fri, Dec 14, 2018, 08:31 Simon Young
wrote:
> Hi Carlos,
>
> Rolling back to 1.13.5 seems to have fixed the issue. I can now run
> multiple consecutive builds and they all pass.
>
> I'm a bit concerned that we're unable to upgrade to the latest version
> though
Hi Carlos,
Rolling back to 1.13.5 seems to have fixed the issue. I can now run
multiple consecutive builds and they all pass.
I'm a bit concerned that we're unable to upgrade to the latest version
though - Do you have enough information to identify the problem?
Thanks,
Simon.
--
You receive
I would rollback to 1.13.5 for now then
On Tue, Dec 11, 2018, 00:49 Simon Young
wrote:
> Hi Carlos,
>
> Thanks for the suggestion. I have tried changing the "Max connections to
> Kubernetes API" and this does have an effect, but not in a way I'd
> expect... I've found that if I change that value
Hi Carlos,
Thanks for the suggestion. I have tried changing the "Max connections to
Kubernetes API" and this does have an effect, but not in a way I'd
expect... I've found that if I change that value in any way at all (either
increase or decrease), then the next build always passes, and all
su
You may be hitting the limit of concurrent connections to k8s api, see
https://github.com/jenkinsci/kubernetes-plugin/blob/master/CHANGELOG.md#1136
On Mon, Dec 10, 2018 at 8:01 AM Simon Young <
simon.yo...@nationaltrust.org.uk> wrote:
> Hi,
>
> We are trying to use the Kubernetes Plugin to run te
Hi,
We are trying to use the Kubernetes Plugin to run tests in a different
container - but *almost* every time we try and execute a command in the
second container, the build fails immediately. I say "almost" because the
build always succeeds after restarting the Jenkins master (or possibly
af
