This is probably related to "Build queue hangs after timer task error". It seems
he started a new thread now that he knows the reason of the jenkins build
hanging out.
But I might be wrong and may be something completely different.
Never used the Jenkins plugin, but I thought it created slaves
+1 to Tims answer. Curious as to what are you trying to solve here ? Could you
explain your use case?
punit agrawal
dev-ops lead
new product development, ebay
On 8/10/18, 2:31 PM, "'Tim Hockin' via Kubernetes user discussion and Q"
wrote:
Well, we're not "starting" the pods, we're
Well, we're not "starting" the pods, we're queuing them up for when
nodes become available. Would you rather they get rejected
immediately? what if a node comes online 3 seconds after that
rejection?
On Fri, Aug 10, 2018 at 2:28 PM Basanta Kumar Panda
wrote:
>
> Hi ,
>
> Here is one of the
Hi ,
Here is one of the Scenario
1. K8S Master is up with 2 slave nodes and is configured to jenkins master.
2. Both the slave nodes are down.
3. Job triggered from jenkins and the job is waiting/hanging.
bash-4.2kubectl get nodes
NAME STATUS ROLES AGE
We usually use regex to get to the pods. You can use it like so
kube_pod_info{pod=~"go-svc.*"}
In the above case, go-svc is the deployment name.
Punit Agrawal
Site Reliability Engineer, Lead
New Product Development
From: on behalf of Nate Rook
Reply-To: "kubernetes-users@googlegroups.com"
Ah, sorry, this is on me. I am specifically concerned with this problem *in
data which is shipped to the monitoring software Prometheus*. I should have
been clearer about kube-state-metrics's remit.
kubediscovery looks quite interesting!
On Friday, August 10, 2018 at 12:09:10 PM UTC-7,
Hi Nate,
We have been working on a tool named 'kubediscovery' to help with
discovering dynamic composition tree of Kubernetes Objects.
You might find it useful for your use-case.
You can find it here:
https://github.com/cloud-ark/kubediscovery
Regards,
Devdatta
Hi,
I wanted to get from a Deployment to its running Pods using some sort of
label join. Getting from Pods to ReplicaSets is easy: the metric
kube_pod_owner connects Pods to their ReplicaSets if they have them. But I
can't find a metric with labels which let me connect ReplicaSets to
Oh, thanks to clarify there was no way to guess that.
And can you see the logs on Kubernetes on why the pod is not created?
kubectl describe pod at least?
On Friday, August 10, 2018, Basanta Kumar Panda
wrote:
> Here is the scenario:
> Basically My Jenkin master is configured with K8S
