8000 Cache the recovery image so can be used later. · Issue #131 · crc-org/snc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Cache the recovery image so can be used later. #131

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.

Sign up for GitHub

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

Jump to bottom
Closed
praveenkumar opened this issue Nov 22, 2019 · 1 comment
Closed

Cache the recovery image so can be used later. #131

praveenkumar opened this issue Nov 22, 2019 · 1 comment

Comments

@praveenkumar
Copy link
Member
praveenkumar commented Nov 22, 2019 •
edited
Loading

We need the recovery image to be cached as part of our snc and that we can use for cert recovery side.
praveenkumar added a commit that referenced this issue Nov 22, 2019
@praveenkumar
Issue #131 Tag cluster-kube-apiserver-operator image
c6e3f61 
We need the image to recover the cert in case it expire, if we don't
tag it properly then we need to do it on the CRC side and that require
the internet connectivity to fetch the hash for KAO image. Now we can
directly use `openshift/cert-recovery` tag without fetching it from the
release payload.
praveenkumar added a commit that referenced this issue Nov 22, 2019
@praveenkumar
Issue #131 Tag cluster-kube-apiserver-operator image
de4ccd5 
We need the image to recover the cert in case it expire, if we don't
tag it properly then we need to do it on the CRC side and that require
the internet connectivity to fetch the hash for KAO image. Now we can
directly use `openshift/cert-recovery` tag without fetching it from the
release payload.
@praveenkumar
Copy link
Member Author

Fixed by #132

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@praveenkumar
0