Skip to content

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

Open
BenTheElder opened this issue Feb 12, 2025 · 3 comments
Open

CI jobs occasionally hitting node not ready #7785

BenTheElder opened this issue Feb 12, 2025 · 3 comments
Labels
sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@BenTheElder
Copy link
Member

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

@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Feb 12, 2025
@BenTheElder
Copy link
Member Author

GKE can't perform maintenance because the Pod Disruption Budget allows for 0 Pod evictions. Update the Pod Disruption Budget.

"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

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2025
@xmudrii
Copy link
Member

xmudrii commented May 14, 2025

This is still the issue occasionally AFAIK
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Development

No branches or pull requests

4 participants