-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubelet: add unit tests for imagePullSecrets keyring #94974
kubelet: add unit tests for imagePullSecrets keyring #94974
Conversation
/assign @derekwaynecarr @dchen1107 @liggitt |
407182d
to
02b5c45
Compare
found: false, | ||
}, | ||
{ | ||
name: "with pull secrets and has default keyring", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens with default keyring and DockerConfigJsonKey or DockerConfigKey that doesn't match the given image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this test case specifically, the default keyring would always return auth configs since the fake Lookup()
call returns hardcoded auth configs. If we used a real keyring it would not return any auth configs if the image didn't match based on the check here:
kubernetes/pkg/credentialprovider/keyring.go
Lines 241 to 245 in 442a69c
// both k and image are schemeless URLs because even though schemes are allowed | |
// in the credential configurations, we remove them in Add. | |
if matched, _ := urlsMatchStr(k, image); matched { | |
ret = append(ret, dk.creds[k]...) | |
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was mostly looking for a test that exercised whether we fell back to the default or not for a DockerConfigJsonKey or DockerConfigKey that doesn't match the given image
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good point. Updated to include tests that only return credentials from the default keyring if DockerConfigJsonKey or DockerConfigKey didn't have a matching image URL passed into Lookup.
02b5c45
to
b18c9b7
Compare
Signed-off-by: Andrew Sy Kim <kim.andrewsy@gmail.com>
b18c9b7
to
44e6998
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewsykim, liggitt 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:
Approvers can indicate their approval by writing |
Signed-off-by: Andrew Sy Kim kim.andrewsy@gmail.com
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Add unit tests for generating kubelet's docker keyring for imagePullSecrets.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: