-
Notifications
You must be signed in to change notification settings - Fork 880
CI jobs occasionally hitting node not ready #7785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
"view details" shows: apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"policy/v1","kind":"PodDisruptionBudget","metadata":{"annotations":{},"labels":{"infra.k8s.io/instance":"gke-prow-build"},"name":"prow-pods","namespace":"test-pods"},"spec":{"maxUnavailable":0,"selector":{"matchLabels":{"created-by-prow":"true"}}}}
creationTimestamp: "2020-09-11T17:30:42Z"
generation: 1
labels:
infra.k8s.io/instance: gke-prow-build
name: prow-pods
namespace: test-pods
resourceVersion: "2676853668"
uid: cc419911-f4a7-4ea6-b995-1a037b62fd6a
spec:
maxUnavailable: 0
selector:
matchLabels:
created-by-prow: "true"
status:
conditions:
- lastTransitionTime: "2024-05-21T11:28:52Z"
message: ""
observedGeneration: 1
reason: InsufficientPods
status: "False"
type: DisruptionAllowed
currentHealthy: 102
desiredHealthy: 0
disruptionsAllowed: 0
expectedPods: 0
observedGeneration: 1 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This is still the issue occasionally AFAIK |
My suspicion is an issue with the approach to pod disruption budget on the GKE clusters. I'm less clear on the AWS clusters.
We've seen similar problems on both.
Filing this as an umbrella to note that we're aware this has happened and to collect examples.
/sig k8s-infra
/sig testing
The text was updated successfully, but these errors were encountered: