updating several diagrams for clarity

[Braundo]

Updating several diagrams for clarity...

1. Replace the architectural diagram (https://kubernetes.io/docs/concepts/architecture/) with the same one from the components page as it covers the same components and concepts, just with different styled diagrams.
2. The Pods image here is confusing. (https://kubernetes.io/docs/concepts/workloads/pods/), this diagram (https://kubernetes.io/images/docs/pod.svg).
3. Added a simple sidecar diagram to accompany the YAML (https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/)
4. Switched from a linked Mermaid diagram to a clearer diagram (https://kubernetes.io/docs/concepts/services-networking/ingress/).
5. Switched from a linked Mermaid diagram to a clearer diagram (https://kubernetes.io/docs/concepts/services-networking/ingress/#simple-fanout)
6. Switched from a linked Mermaid diagram to a clearer diagram (https://kubernetes.io/docs/concepts/services-networking/ingress/#name-based-virtual-hosting)
7. Controlling access diagram is confusing and looks outdated. (https://kubernetes.io/docs/concepts/security/controlling-access/)
8. Change from Mermaid to SVG diagram for better clarity (https://kubernetes.io/docs/concepts/cluster-administration/node-autoscaling/)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lmktfy for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• content/en/docs/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	b338433
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/6901377da3620500092c34e7
😎 Deploy Preview	https://deploy-preview-52980--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[lmktfy]

Thanks. The new files belong with the English content, though. New diagram content shouldn't go inside static.

[Braundo]

I think I got them all 😄

[lmktfy]

Once this is all looking OK and previews how you expect it, please squash the commits in this PR.

[Braundo]

Thanks for raising the point about images in static ... I agree that keeping images in content/en/... is important for localization.

Right now each of these diagrams does live under content/en/docs/images/ for the English source of truth. But I also added copies under static/images/docs/ because without that, the new diagrams weren't being published at /images/docs/... in the Netlify preview (and they 404'd when referenced from the docs pages). That meant the figures rendered with captions but the images themselves were broken.

I’m definitely happy to follow the preferred pattern here. If there’s an existing mount or publishing step we should be using so that new images from content/en/docs/images/ get served at /images/docs/... without needing them in static/, I can update this PR to do that instead.