Kubernetes

Starting with Renovate 24.40.0, the renovate process finishes its work but never exits, hanging the Kubernetes cronjob pod. The cause was the AWS SDK ECR client keeping a connection open, so the node process stayed alive.

supporting2026-09-23 23:05 UTC

On self-hosted Sentry, the JavaScript loader shown in Client Keys (DSN) settings produces only this: `function _sentry_noopWarning() { console.warn("The Sentry loader you are trying to use isn't working anymore, check your configuration.");

incidental2026-09-23 21:30 UTC

Running CockroachDB (insecure mode) as a StatefulSet on GKE with Istio injected, cockroach sql --insecure failed with connection refused even though the pods were running. The root cause discussed in the thread: the install manifests name t

primary2026-09-23 13:30 UTC

Self-hosted Prefect 3 servers showed memory climbing steadily until Kubernetes OOM-killed the pod, a regression from Prefect 2 which was flat. The reporter ran without Redis and noted Prefect 2 had no such problem. Prefect maintainers and c

supporting2026-09-23 13:11 UTC

Upgrading Flipt from 1.8.3 to 1.9.0 or 1.10.0 breaks Postgres connectivity in Kubernetes with: getting db driver for: postgres: dial tcp: lookup postgres.database.svc.cluster.local: device or resource busy. Versions 1.8.2 and 1.8.3 worked f

supporting2026-09-23 13:04 UTC

After upgrading to Kubernetes 1.29, the Lacework agent logs show it querying APIs that were removed in 1.29, like the flowcontrol v1beta2 resources. The worry is the agent will break against the removed APIs.

primary2026-09-23 12:06 UTC

Flipt v2.0.1 in Kubernetes consumes 550-800 MB of memory with only 4 flags, configured with 4 environments backed by 2 git storage projects. The git repositories are GitOps repos for ArgoCD with substantial history, and Flipt appeared to ho

supporting2026-09-23 12:06 UTC

Running the Datadog Agent container with a read-only root filesystem: the agent dies on startup with `ln: failed to create symbolic link '/etc/datadog-agent/datadog.yaml': Read-only file system` and `rm: cannot remove ... Read-only file sys

supporting2026-09-23 12:04 UTC

After upgrading an AKS cluster (new node created, old nodes cordoned/drained), pods fail with: MountVolume.SetUp failed for volume ... : kubernetes.io/csi: mounter.SetUpAt ... "driver name secrets-store.csi.k8s.io not found in the list of r

supporting2026-09-23 12:03 UTC

Running the Chainguard nginx image with a read-only filesystem fails: docker run -it -p 8080:8080 --read-only --tmpfs /tmp cgr.dev/chainguard/nginx:latest gives s6-svscan: fatal: unable to mkdir .s6-svscan: Read-only file system. Security b

supporting2026-09-23 12:02 UTC

The docs show Dagger running from many CI systems, but not how to run Dagger itself inside a container, such as a Kubernetes pod, without needing docker socket access or a privileged container. The answer for Kubernetes, Argo Workflows, and

primary2026-09-23 12:02 UTC

Syncing a docker registry secret from AWS Secrets Manager into a Kubernetes dockerconfigjson secret via an ExternalSecret template fails with: Secret "docker-registry" is invalid: data[.dockerconfigjson]: Invalid value: "...": invalid chara

supporting2026-09-23 11:59 UTC

Deploying 1Password Connect in Kubernetes with the official Helm chart, connect-sync fails with: (E) Server: (unable to get credentials and initialize API...), Wrapped: (LoadLocalAuthV2 failed to credentialsDataFromBase64), illegal base64 d

primary2026-09-23 11:57 UTC