feat(renovate): Wait 2 days to use latest k8s

[kiblik]

When a new k8s is released, tests with Minikube are failing because it is not fully ready to use the latest version. If Renovate waits 2 days, nothing critical will happen, and the review process will be much smoother (no need to troubleshoot why tests are failing).

[dryrunsecurity]

This pull request introduces a 2-day deliberate delay for automated Kubernetes dependency updates via a minimumReleaseAge setting, which could leave the system exposed to newly disclosed high-severity vulnerabilities for up to 48 hours. While not flagged as blocking, this configuration increases security risk by postponing the application of critical patches.

Delayed Security Patching for Kubernetes in .github/renovate.json

Vulnerability	Delayed Security Patching for Kubernetes
Description	The configuration introduces a 'minimumReleaseAge' of '2 days' for Kubernetes dependencies. This intentionally delays automated updates, including critical security patches, for 48 hours. This delay creates a window of exposure where the system could remain vulnerable to newly disclosed high-severity exploits before a patch is applied.

django-DefectDojo/.github/renovate.json

Lines 40 to 43 in 779f958

	"minimumReleaseAge": "2 days"
	}],
	"customDatasources": {
	"endoflife-oldest-maintained": {

---

All finding details can be found in the DryRun Security Dashboard.

[mtesauro]

Approved