Add blog post about publishing Kubernetes SIG images to registry.k8s.io

[kahirokunn]

Description

This PR adds an English Kubernetes contributor blog post about publishing a Kubernetes SIG's container images through registry.k8s.io.

Moved from kubernetes/website#56246 after blog team feedback that the content is more appropriate for kubernetes/contributor-site.

The post uses the secretreader and kubeconfig-secretreader images of cluster-inventory-api as a concrete example.
It explains why GHCR is not the official distribution path for Kubernetes project images, then documents the first-time setup across:

• image-owning repository
• kubernetes/k8s.io
• kubernetes/test-infra
• kubernetes/org

It also includes three SVG diagrams that compare the GHCR and official publication paths and show the dependency order for first-time registry.k8s.io setup.

SIG feedback

https://kubernetes.slack.com/archives/CCK68P2Q2/p1785504175857279

Issue

N/A

/area blog
/sig multicluster

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• content/en/blog/OWNERS

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

[KashishV999]

Hi , thank you for your work

Here are some things after re-reviewing

1. The blog itself repeats same things so many times :
   Eg : 18-character limit is there is 3 places :
   The staging access group name. Its suffix has an 18-character limit.
access group name has an 18-character limit on its suffix
Check that the group name fits the 18-character limit.

and this is one such example , so many things have been repeated across Part 1 and 2.
Both parts explain same things at same depth (which make repetitive and too lengthy)

and the names of both parts if you think means literally same : "the road to publi..." and "how to publish ..

2. I apologise for having to ask this. I think the writing style reads like it may have gone through AI editing or AI generation. Was that intentional?

3. The starting of blog starts too abrupt , try to keep it light for readers
   This types of blog is more like a how-to guide for reader , so have an intro for an overall concept of the blog , then maybe explain your original plan and issue you faced , then just start how to guide : (IMO no need to have 2 parts until and unless both are talking about 2 very separate concerns)
   This is just my personal opinion ,feel free to add your suggestions

4. Also in a few spots, I see the blog is including too many small details without adding more meaning to it.
   Its extremely important to value reader's time :
   For eg : In 2. Rebuilding the release workflow part quoting a Slack message in full and then repeating it , can be compacted and be made more reader-friendly.

Considering these reviews , the blog do need to be at a quality level that we can accept,
If you're willing to rewrite this, it'd be great to get it merged and ready to publish :)

[kahirokunn]

@KashishV999 Thanks for the feedback 🙏
I do use AI to help with editing. I went through all the points you raised and rewrote the post quite extensively to address them. I’d appreciate another look when you have time. 🙇‍♂️

[KashishV999]

Hi: I extensively reviewed this blog , added suggestions that maybe be worth looking and some tips that might help you in your future blogs ,
Please have a look at each review and apply the suggestions :)

Btw check this documentions: these are great resources (not sure why you didn't added)

• https://github.com/kubernetes/k8s.io/tree/main/registry.k8s.io
• https://github.com/kubernetes-sigs/promo-tools/blob/main/docs/promotion-pull-requests.md
• https://github.com/kubernetes/test-infra/blob/master/config/jobs/image-pushing/README.md

(Also I wonder if these resources already exist, do you think you were not able to find these resources/or you think the documentation was not good enough for a contributor to follow the process across various repository that it inspired you to write a blog in first place (asking cause it will help us to improve our documentation better)? )

[kahirokunn]

Thanks for taking the time to review this so thoroughly! I’ve gone through the comments and applied the suggestions. And yeah, I did find some of those docs along the way. The tricky part was figuring out how the pieces across the different repos fit together, and what order everything needed to happen in. The individual docs were helpful, but I kept wishing there was one end-to-end guide. That’s what made me want to write this post.

[KashishV999]

Thank @kahirokunn for your work
/lgtm

[kahirokunn]

Thanks! And thank you for the review, it was a big help. 🙏

[KashishV999]

/sig k8s-infra
Adding for visibility

[kubernetes-prow]

@KashishV999: The label(s) sig/adding, sig/for, sig/visibility cannot be applied, because the repository doesn't have them.

Details

In response to this:

/sig k8s-infra Adding for visibility

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[KashishV999]

Hey @kahirokunn, nice writeup!
Moving forward, to ensure enough visibility across the respective SIG and maintainers, and to make sure the blog correctly represents the SIG:

1. Could you post this PR link in #sig-k8s-infra on Slack for visibility and asking feedback if any /or if it correctly represents the SIG , Also maybe you want to include preview Link : Preview URL ?
2. and also link that slack thread back in the PR description and update us by commenting once done?

and after this draft get merged , we urge you to update the specific sig regarding the publishing date for this blog once we set it.

Thanks and have a great day :)

[kahirokunn]

Thanks for pointing this out. I’ve shared the post in #sig-k8s-infra and added the thread to the PR description.
Posting an update here. Thanks again for your help!

[TineoC]

Suggested change

	Note: Staging registries have a 90-day retention policy and are intended only
	for intermediate builds. End users should consume images from
	`registry.k8s.io` after they have been promoted.
	{{< alert color="info" title="Note" >}}
	Staging registries have a 90-day retention policy and are intended only
	for intermediate builds. End users should consume images from
	`registry.k8s.io` after they have been promoted.
	{{< /alert >}}