-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add a simple e2e test for the task #5
Conversation
401eee7
to
bb58675
Compare
Signed-off-by: Vincent Demeester <[email protected]>
bb58675
to
c6961ad
Compare
Signed-off-by: Vincent Demeester <[email protected]>
Signed-off-by: GitHub <[email protected]>
Signed-off-by: GitHub <[email protected]>
Signed-off-by: GitHub <[email protected]>
Signed-off-by: GitHub <[email protected]>
cc @Senjuti256 |
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.
Looks good to me @vdemeester .
kubectl delete secret regcred || true | ||
run kubectl create secret generic regcred \ | ||
--from-file=.dockerconfigjson=$HOME/.docker/config.json \ | ||
--type=kubernetes.io/dockerconfigjson | ||
assert_success | ||
run kubectl patch serviceaccount default -p '{"imagePullSecrets": [{"name": "regcred"}]}' | ||
assert_success |
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.
Are we adding this so that we don't face any permission denial issue while accessing the image from registry.redhat.io . Is it because we didn't find any oc image in registry.access.redhat.com ?
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.
Yes. Some images are not exposed through registry.access.redhat.com
so, I went with having some credentials instead.
Signed-off-by: Vincent Demeester [email protected]