gcr.io/google-containers still used in current docs

[BenTheElder]

This is a Bug Report

Problem:

There are still apparently active docs using this outdated image host, it should be replaced by registry.k8s.io which has all images + newer ones and is controlled fully by the community.
https://cs.k8s.io/?q=gcr.io%2Fgoogle-containers&i=nope&files=&excludeFiles=&repos=kubernetes/website

Proposed Solution:

I suspect we shouldn't touch the blog posts, but should update:

content/en/docs/tasks/debug/debug-application/debug-service.md

Page to Update:
https://kubernetes.io/docs/tasks/debug/debug-application/debug-service/

[BenTheElder]

k8s.gcr.io should be replaced as well.

I was going to file a PR for this, but I'm not sure if we want to keep using this unpatched busybox image.

Maybe agnhost again?

[thisisharrsh]

/sig docs

[thisisharrsh]

/language en

[sftim]

/triage accepted
/priority important-longterm

[iheartNathan]

/assign

[BenTheElder]

I was going to file a PR for this, but I'm not sure if we want to keep using this unpatched busybox image.

Maybe agnhost again?

Anyone have thoughts on this? Technically we could just file a trivial "replace gcr.io/google-containers with registry.k8s.io", but any image that was on gcr.io/google-containers is really old / unpatched, and we aren't currently maintaining busybox image for any project.

SIG Testing has previously offered up agnhost image for this sort of debugging, but it is technically developed for e2e testing Kubernetes. It is however actively maintained / published. It may not be drop-in compatible depending on usage.

[stmcginnis]

+1 for agnhost for me. Forcing some minor tweaks to work with the new image seems better to me than having everyone use an old and unpatched image. IIRC there were some arm64 compatibility concerns as well.