Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@runcom
Copy link
Member

@runcom runcom commented Apr 10, 2017

Fix the following upstream k8s's e2e-node test:

should be able to pull from private registry with secret [Conformance]

Signed-off-by: Antonio Murdaca [email protected]

@runcom runcom added this to the 0.0.2 milestone Apr 10, 2017
@runcom
Copy link
Member Author

runcom commented Apr 10, 2017

@mrunalp @sameo PTAL

@runcom runcom modified the milestones: 0.2, 0.0.2 Apr 10, 2017
DockerAuthConfig: &types.DockerAuthConfig{
Username: username,
Password: password,
},
Copy link

Choose a reason for hiding this comment

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

I assume this will be a NOOP when username and password are nil ?

Copy link
Member Author

Choose a reason for hiding this comment

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

not actually, I re-pushed a fixed version I guess. If those are empty, we'll simply not read the .docker/config.json. The latest revision makes sure not to send anything if password is empty.

@runcom runcom force-pushed the image-pull-secret branch from 71da71a to c3360b6 Compare April 10, 2017 14:38
options := &copy.Options{}
// a not empty password should be sufficient to decide whether to send auth
// or not I guess
if password != "" {
Copy link

Choose a reason for hiding this comment

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

Although I can see people using password less accounts, I really don't know how they could have username less ones. So I'd use username not being empty as a criteria to send auth, instead of password.

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed

Fix the following upstream k8s's e2e-node test:
```
should be able to pull from private registry with secret [Conformance]
```

Signed-off-by: Antonio Murdaca <[email protected]>
@runcom runcom force-pushed the image-pull-secret branch from c3360b6 to 05cde3e Compare April 10, 2017 15:10
@sameo
Copy link

sameo commented Apr 10, 2017

LGTM

1 similar comment
@mrunalp
Copy link
Member

mrunalp commented Apr 10, 2017

LGTM

@mrunalp mrunalp merged commit 32750cd into cri-o:master Apr 10, 2017
@mrunalp
Copy link
Member

mrunalp commented Apr 10, 2017

@sarahnovotny @yujuhong Can we get @sameo setup with commit access to the repo?

@runcom runcom deleted the image-pull-secret branch April 10, 2017 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants