Skip to content
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

Merged
merged 6 commits into from
Nov 22, 2023
Merged

Add a simple e2e test for the task #5

merged 6 commits into from
Nov 22, 2023

Conversation

vdemeester
Copy link
Member

Signed-off-by: Vincent Demeester [email protected]

@vdemeester vdemeester force-pushed the add-e2e-tests branch 8 times, most recently from 401eee7 to bb58675 Compare November 21, 2023 20:33
Signed-off-by: Vincent Demeester <[email protected]>
@vdemeester
Copy link
Member Author

cc @Senjuti256

@vdemeester vdemeester merged commit 231b84b into main Nov 22, 2023
1 check passed
@vdemeester vdemeester deleted the add-e2e-tests branch November 22, 2023 14:49
Copy link
Contributor

@Senjuti256 Senjuti256 left a 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 .

Comment on lines +14 to +20
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
Copy link
Contributor

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 ?

Copy link
Member Author

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.

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.

2 participants