Conversation
|
Images are ready for the commit at ee64638. To use with deploy scripts, first |
365acec to
b34c8a2
Compare
b34c8a2 to
6f1c8a0
Compare
5b3627f to
5bfbc5d
Compare
|
/test |
|
@theencee: The
The following commands are available to trigger optional jobs:
Use
DetailsIn response to this:
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/test-infra repository. |
|
/test gke-postgres-scale-tests |
5bfbc5d to
d0a9c09
Compare
|
/retest |
1 similar comment
|
/retest |
cbc675b to
fda29d1
Compare
|
/test gke-postgres-qa-e2e-tests gke-qa-e2e-tests |
fda29d1 to
cd9c1ac
Compare
|
/test gke-postgres-qa-e2e-tests gke-qa-e2e-tests |
1 similar comment
|
/test gke-postgres-qa-e2e-tests gke-qa-e2e-tests |
cd9c1ac to
be74716
Compare
User request: Fix multi-arch image loading issue in PR #18867 where Kind fails to load images with error "content digest not found" for arm64 layers. Problem: kind load docker-image uses docker save and ctr images import --all-platforms internally. When docker pull fetches multi-arch images, even with --platform flag, docker save includes manifest index references. The ctr import then fails because arm64 layers referenced in the manifest aren't present. Solution: Bypass "kind load docker-image" entirely by pulling images directly inside the Kind node using ctr. This avoids the docker save/import dance and the --all-platforms issue. Approach: 1. Use docker exec to run ctr inside the Kind node 2. Pull with --platform linux/amd64 to get only the needed variant 3. Pass quay.io credentials via --user flag to ctr This is a recommended workaround from kubernetes-sigs/kind issues #3795, #3845, and #4066, which document this as a known issue with Docker 29 and containerd. References: - kubernetes-sigs/kind#4066 - kubernetes-sigs/kind#3845 - kubernetes-sigs/kind#3795 Code changes developed with AI assistance. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Description
Grabbed a nginx image (nginx:1.22-alpine) and tagged it as qa:latest. This prevents rate limiting or slow down from docker.io from impacting these tests
Checklist
If any of these don't apply, please comment below.
Testing Performed
this is a test
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.