-
Notifications
You must be signed in to change notification settings - Fork 52
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
feat: linking mounted certificates from '/var/run/secrets/kubernetes.io/serviceaccount' to '/$HOME/.config/containers/certs.d' before podman login #851
Conversation
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-851 |
1 similar comment
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-851 |
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-851 |
Strange, I can't pull the image
|
|
…io/serviceaccount' to '/$HOME/.config/containers/certs.d' before podman login Signed-off-by: Ilya Buziuk <[email protected]>
@tolusha nice catch, handling special case for kube:admin as part of the script |
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-851 |
I spotted another problem while testing with ClusterBot
|
hmm, did a test on a fresh hypershift cluster and with kube:admin got the following error during image pulling:
[1] https://docs.podman.io/en/latest/markdown/podman-system-migrate.1.html |
…gin' Signed-off-by: Ilya Buziuk <[email protected]>
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-851 |
@tolusha with the recent changes the image pulling should work with both hypershift / aws, and rosa. I believe the previous issue was related to $USER env var. |
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-851 |
…'podman login' Signed-off-by: Ilya Buziuk <[email protected]>
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-851 |
@ibuziuk: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
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.
Checked with Eclipse Che Next + quay.io/eclipse/che-dashboard:pr-851
Following test scenario from PR description, image-registry.openshift-image-registry.svc:5000/openshift/cli:latest had been pulled correctly from within Empty workspace and spring-petclinic workspace using tools container, being logged into the Eclipse Che as user with and without cluster admin rights:
IMHO, with that results PR has satisfied DoD of fixing issue eclipse-che/che#22140
Well done, @ibuziuk !
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dmytro-ndp, ibuziuk, l0rd, tolusha The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Build 3.8 :: dashboard_3.x/284: Console, Changes, Git Data |
Build 3.8 :: sync-to-downstream_3.x/3745: Console, Changes, Git Data |
What does this PR do?
Linking mounted certificates from '/var/run/secrets/kubernetes.io/serviceaccount' to '/$HOME/.config/containers/certs.d' before podman login
What issues does this PR fix or reference?
eclipse-che/che#22140
Is it tested? How?
Install Eclipse Che and replace the dashboard image related to the PR
Create an empty workspace, open the terminal, and execute
podman pull image-registry.openshift-image-registry.svc:5000/openshift/cli:latest
N.B. symbolic links for
ca.crt
andservice-ca.crt
are in the$HOME/.config/containers/certs.d/image-registry.openshift-image-registry.svc:5000
folderRelease Notes
Docs PR
Related info - https://manpages.ubuntu.com/manpages/impish/man5/containers-certs.d.5.html