Update Kubernetes executor service container naming documentation
What does this MR do?
fix: update k8s service container naming docs to reflect alias-based naming (closes #39235 (closed))
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Why was this MR needed?
In the context of this issue, the problem was that an admission controller was likely targeting service containers by name — for example, applying a policy specifically to containers named svc-0 or svc-1. When !4469 (merged) changed the naming so that containers with aliases get named after those aliases instead (e.g. postgres instead of svc-0), the admission controller no longer recognized those containers. Its rules silently stopped applying, which could mean security policies or resource constraints weren't being enforced anymore.
What's the best way to test this MR?
Check that the markdown renders correctly in the docs.