Kubernetes 1.36: gitRepo volumes reach the end of the road

A removal worth finding

In this retrospective April review, Kubernetes 1.36, released on April 22, 2026, permanently disables the gitRepo volume. The mechanism can no longer be re-enabled. Release announcement.

Find quiet dependencies

The issue primarily concerns old manifests and deployment templates copied between projects. Before an upgrade, searching both source files and actually deployed objects helps define the work. Absence from a recent repository does not fully describe a cluster retaining older workloads. For an application service, the key question is exactly how its code reaches the container.

Make delivery explicit

A migration can be a chance to evaluate an application image whose contents are built and identified in advance. If downloading code at startup remains necessary, its permissions and reference deserve separate examination. The choice depends on a real requirement. A configuration accepted by the new API proves neither successful application startup nor reproducible contents: those two points need their own verification.