Skip to content

docs: clarify registry addon workaround for cri-o#22809

Open
iacker wants to merge 1 commit intokubernetes:masterfrom
iacker:docs/registry-crio-note
Open

docs: clarify registry addon workaround for cri-o#22809
iacker wants to merge 1 commit intokubernetes:masterfrom
iacker:docs/registry-crio-note

Conversation

@iacker
Copy link
Copy Markdown

@iacker iacker commented Apr 7, 2026

Summary

  • clarify that the existing localhost:5000 registry addon workflow is Docker-oriented
  • document the CRI-O workaround of using the in-cluster registry Service IP and port 80 in workload image references
  • point readers to the image pushing handbook for workflows that avoid relying on a dynamic Service IP

Validation

  • cd site && npm ci
  • independent content review against the issue discussion and existing registry docs
  • note: no dedicated site build target was available via make -C site build in this checkout

Fixes #6982

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: iacker
Once this PR has been reviewed and has the lgtm label, please assign medyagh 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:

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

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 7, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

Hi @iacker. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@minikube-bot
Copy link
Copy Markdown
Collaborator

Can one of the admins verify this patch?

@k8s-triage-robot
Copy link
Copy Markdown

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

update registry addon documentation

4 participants