Drop vendor registry details from container image concept

[sftim]

Minimal rewrite to avoid referencing specific 3rd party vendors and their implementations.

Helps with #20232 and #21641

The amended page still needs work; that's OK, that's something we can pick up in a separate pull request.

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit 225517a

https://deploy-preview-21438--kubernetes-io-master-staging.netlify.app

[celestehorgan]

@sftim to be clear: when you say "The amended page still needs work;" – do you want review on grammar/language here or just for me to catch the typos and let you go on your merry way? :)

[sftim]

So long as these changes have no regressions, let's merge.

[jimangel]

Do we want to replace all capture statements too?

[sftim]

Yes we do!

[zacharysarah]

Alas! Merge conflict, likely from #21359!

[jimangel]

Re-triggered the build it had a strange memory error.
/lgtm

[jimangel]

Failed again.... the logs:

9:29:19 AM: hugo --enableGitInfo --buildFuture -b https://deploy-preview-21438--kubernetes-io-master-staging.netlify.app
9:29:19 AM: Building sites …
9:29:21 AM: panic: runtime error: invalid memory address or nil pointer dereference
9:29:21 AM: [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x109ad12]
9:29:21 AM: goroutine 84 [running]:
9:29:21 AM: github.com/gohugoio/hugo/hugolib.(*shortcodeHandler).extractShortcode(0xc0069b6c80, 0xb, 0x0, 0xc005a11090, 0x0, 0x0, 0x1a14380)
9:29:21 AM: 	/root/project/hugo/hugolib/shortcode.go:505 +0x882

9:29:21 AM: ┌─────────────────────────────┐
9:29:21 AM: │   "build.command" failed    │
9:29:21 AM: └─────────────────────────────┘
9:29:21 AM: ​
9:29:21 AM:   Error message
9:29:21 AM:   Command failed with exit code 2: make deploy-preview
9:29:21 AM: ​
9:29:21 AM:   Error location
9:29:21 AM:   In build.command from netlify.toml:
9:29:21 AM:   make deploy-preview
9:29:21 AM: ​
9:29:21 AM:   Resolved config
9:29:21 AM:   build:
9:29:21 AM:     command: make deploy-preview
9:29:21 AM:     functions: /opt/build/repo/functions
9:29:21 AM:     publish: /opt/build/repo/public

[tengqm]

(re)approve
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

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

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [tengqm]

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

[et304383]

@sftim What was the rationale for this change and where are the replacement docs that explain that K8s will automatically authenticate against AWS ECR periodically if running on EC2 with the appropriate IAM role permissions?

I just wasted a day trying to understand how K8s was authenticating in AWS when trying to replicate our cluster in OCI, and without this documentation there is NOTHING on the Internet that explains that K8s does this automatically.

[sftim]

This change helped with two issues: #20232 and #21641.
Kubernetes itself does not periodically authenticate against Amazon ECR. However, EC2 instances running with a particular AMI on AWS may well do that. For details on how a particular cloud provider has set up their flavor of Kubernetes, it is best to check the documentation provided by that cloud provider.

The blog article https://kubernetes.io/blog/2020/05/third-party-dual-sourced-content/ provides more content about why Kubernetes avoids documenting external / third party software.

[et304383]

This change helped with two issues: #20232 and #21641. Kubernetes itself does not periodically authenticate against Amazon ECR. However, EC2 instances running with a particular AMI on AWS may well do that. For details on how a particular cloud provider has set up their flavor of Kubernetes, it is best to check the documentation provided by that cloud provider.

Actually, it does, because we're using a non managed Kubernetes on AWS EC2 with IAM roles granting ECR access and it just works.

The K8s documentation used to state this is how it works (based on the French page). We're running on version 1.17. Are you saying this functionality is removed in later versions?

[sftim]

The Kubernetes documentation no longer includes documentation for third-party systems and software, other than those components necessary for Kubernetes to run.

It's possible that the kubelet does include an integration with AWS IAM and AWS ECR; if so, that's news to me. We'd be happy to document that functionality (perhaps in a different way) if it does exist as part of Kubernetes itself because that would then be built in to Kubernetes.