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.

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

Support OpenShift 4.2 Airgap mode (use image digests) #15350

Closed
3 tasks done
l0rd opened this issue Nov 28, 2019 · 3 comments
Closed
3 tasks done

Support OpenShift 4.2 Airgap mode (use image digests) #15350

l0rd opened this issue Nov 28, 2019 · 3 comments
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Milestone
7.16

Comments

@l0rd
Copy link
Contributor

l0rd commented Nov 28, 2019 •
edited by tolusha
Loading

Is your enhancement related to a problem? Please describe.

In order to leverage OpenShift Airgap mode that is available since 4.2 there are some rule that we should follow in the Operator design/behavior. In particular all images should be referred using their digest rather then a tag.

Describe the solution you'd like

There are a few documents with the recommendations:
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 28, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 28, 2019
@slemeur slemeur added kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. and removed kind/enhancement A feature request - must adhere to the feature request template. labels Nov 28, 2019
@tsmaeder tsmaeder added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Nov 28, 2019
@l0rd l0rd removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 29, 2019
@l0rd l0rd removed the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Dec 12, 2019
@nickboldt nickboldt added team/deploy status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach and removed status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Jan 6, 2020
@davidfestal davidfestal mentioned this issue Jan 29, 2020
Closed
@nickboldt nickboldt added this to the 7.10.0 milestone Feb 11, 2020
@nickboldt
Copy link
Contributor

Slipping to 7.10 as something to prioritize for the quarter after CRW 2.1 is done. cc: @davidfestal @l0rd

@tolusha tolusha mentioned this issue Mar 4, 2020
Closed
@nickboldt nickboldt mentioned this issue Mar 9, 2020
Closed
@nickboldt nickboldt modified the milestones: 7.10.0, 7.11.0 Mar 12, 2020
@nickboldt nickboldt modified the milestones: 7.11, 7.12 Apr 8, 2020
@nickboldt nickboldt mentioned this issue Apr 17, 2020
Merged
@nickboldt nickboldt modified the milestones: 7.12, 7.13 Apr 29, 2020
@nickboldt
Copy link
Contributor

Given no news, assuming slipped to 7.13.

@tolusha tolusha mentioned this issue May 6, 2020
Closed
@tolusha tolusha modified the milestones: 7.13, 7.14 May 21, 2020
@nickboldt nickboldt modified the milestones: 7.14, Backlog - Deploy Jun 22, 2020
@nickboldt
Copy link
Contributor

Not done in 7.14, and won't be done in 7.15 (sprint ends in 2 days) so punting to backlog.

@l0rd l0rd mentioned this issue Jul 1, 2020
Closed
@tolusha tolusha closed this as completed Jul 8, 2020
@tolusha tolusha modified the milestones: Backlog - Deploy, 7.16 Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Milestone
7.16
Development

No branches or pull requests
6 participants
@nickboldt @l0rd @slemeur @tolusha @tsmaeder @che-bot