Skip to content

Use Docker registry mirror if available#147

Merged
kcp-ci-bot merged 2 commits intokcp-dev:mainfrom
xrstf:registry-mirror
Feb 6, 2026
Merged

Use Docker registry mirror if available#147
kcp-ci-bot merged 2 commits intokcp-dev:mainfrom
xrstf:registry-mirror

Conversation

@xrstf
Copy link
Copy Markdown
Contributor

@xrstf xrstf commented Feb 5, 2026

Summary

This PR reconfigures the docker-in-docker daemon that we use inside the Prowjob to build the operator and then to run the kind cluster, to use the newly installed Docker registry cache in our CI environment.

This approach is copy-pasted from what works very reliably at Kubermatic: To make the mirror available inside kind, we use socat to create a socket file that can be mounted into the kind cluster, and socat then simply forwards to the actual registry mirror.

What Type of PR Is This?

/kind cleanup

Release Notes

NONE

On-behalf-of: @SAP christoph.mewes@sap.com
@kcp-ci-bot kcp-ci-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has signed the DCO. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 5, 2026
@xrstf
Copy link
Copy Markdown
Contributor Author

xrstf commented Feb 5, 2026

/retest

On-behalf-of: @SAP christoph.mewes@sap.com
@xrstf
Copy link
Copy Markdown
Contributor Author

xrstf commented Feb 6, 2026

/retest

@xrstf xrstf changed the title WIP - use Docker registry mirror if available Use Docker registry mirror if available Feb 6, 2026
@kcp-ci-bot kcp-ci-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 6, 2026
@xrstf
Copy link
Copy Markdown
Contributor Author

xrstf commented Feb 6, 2026

/kind cleanup

@kcp-ci-bot kcp-ci-bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Feb 6, 2026
Copy link
Copy Markdown
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
:shipit:

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2026
@kcp-ci-bot
Copy link
Copy Markdown
Contributor

LGTM label has been added.

DetailsGit tree hash: 8ffb9a2437aa748a4b6daceba638f886cb97c101

@xrstf
Copy link
Copy Markdown
Contributor Author

xrstf commented Feb 6, 2026

/approve

@kcp-ci-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii, xrstf

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

The pull request process is described 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

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2026
@kcp-ci-bot kcp-ci-bot merged commit 7ec72e1 into kcp-dev:main Feb 6, 2026
12 checks passed
@xrstf xrstf deleted the registry-mirror branch February 12, 2026 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants