Incident Library
Applied filters SymptomImage pull failuresFactorCache-masked failureDomainKubernetesClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    At 1:47am GMT on 28 October 2025, Harness's automated synthetic checks that simulate SDK traffic for the Feature Flags service began failing, and some requests to http://config.ff.harness.io/client/auth received 502 responses.

    Trigger

    During a routine deployment, Kubernetes rescheduled some pods of a Feature Flags dependency onto new nodes that did not have the image cached locally.

    Root cause
    Component
    Contributing factor
    Detection

    Automated synthetic checks that simulate SDK traffic for the Feature Flags service began failing at 1:47am GMT.

    Remediation
    • Restored the missing image to Google Artifact Registry
    • Redeployed the impacted pods
    Action items
    • Review and strengthen the image retention policies in Google Artifact Registry to prevent unintended deletions
    • Validate automatically that all production images are kept for a defined minimum period
    • Add monitoring and alerting for image pull errors
Check your cluster for this

This case involves Container registry and its credentials. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1