Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

Hi all, Can anyone please help with the following error Error from server (Forbidden): pods is forbidden: User "system:anonymous" cannot list pods in the namespace "default" Setup Kubernetes CLI (kubectl) Options: Kubernetes server endpoint -> server from config (ex: https://ip:6443) Certificate

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

OOMKilled has nothing to do with the host resources, but the process in the container using more memory than available. Try increasing the memory limits and read https://blog.csanchez.org/2017/05/31/running-a-jvm-in-a-container-without-getting-killed/ On Thu, Feb 22, 2018 at 10:19 AM,

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

Disk space and memory are all at an extremely low utilization for all of my hosts. So it's not real resource exhaustion. I'm thinking timeline wise it seems that OOMkilled state is possibly a result of kubernetes terminating the pod due to disconnection. INFO: Excess workload after pending

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

I'm actually seeing now that the workers are being OOMkilled at some point. Which doesn't make any sense because all of my kubernetes workers have >50gb free and this pod only requires 256mb. Name: jnlp-1sh50 Namespace:jenkins-test Node: kubeworker-rwva1-prod-10/10.0.0.217

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

That log suggests that the slave is not "online" for jenkins. If you go to the jenkins nodes page under /computer/ what do you see? maybe the slave is offline for some reason, lack of space or something On Wed, Feb 21, 2018 at 9:25 PM, wrote: > I've downgraded to the 1.2

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

I've downgraded to the 1.2 version of the plugin and gone through the debug steps listed here https://github.com/jenkinsci/kubernetes-plugin No luck. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

-- 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

Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can

On Monday, February 19, 2018 at 9:02:22 PM UTC-8, Brandon wrote: > > Hello, I am trying to use the community helm chart for Jenkins and the > Kubernetes plugin 1.2 so that agents can be dynamically provisioned >