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

Verify Che 6 to Che 7 upgrade using operator works for all updated containers #14864

Closed
nickboldt opened this issue Oct 11, 2019 · 2 comments
Closed

Verify Che 6 to Che 7 upgrade using operator works for all updated containers #14864

nickboldt opened this issue Oct 11, 2019 · 2 comments
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@nickboldt
Copy link
Contributor

nickboldt commented Oct 11, 2019 •
edited
Loading

Followup from #14200

Is your task related to a problem? Please describe.

Goal here is to verify that an old Che 6.x install using old containers can be updated to new 7.3 using newer containers, via an operator-based update as discussed in #14200 (comment) (and below).

  • PVC: registry.access.redhat.com/ubi8-minimal:8.0-159 -> registry.access.redhat.com/ubi8-minimal:8.0-213
  • Postgres: centos/postgresql-96-centos7:20190912-81b8a3a to centos/postgresql-96-centos7:9.6
  • Che Server eclipse/che-server:6.19.0 to eclipse/che-server:7.2.0
  • keycloak eclipse/che-keycloak:6.19.0 to eclipse/che-keycloak:7.2.0

Describe the solution you'd like

Automated test that will:

  • install old Che 6.19 via operator, with custom image versions noted above
  • cause update to occur to update to newer 7.x operator, with default images set
@nickboldt nickboldt added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Oct 11, 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 Oct 11, 2019
@nickboldt nickboldt mentioned this issue Oct 11, 2019
Closed
@tolusha tolusha added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator severity/P1 Has a major impact to usage or development of the system. labels Oct 12, 2019
@tolusha
Copy link
Contributor

tolusha commented Oct 12, 2019

/cc @davidfestal

@tolusha tolusha added area/dashboard area/install Issues related to installation, including offline/air gap and initial setup and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 12, 2019
@tolusha
Copy link
Contributor

tolusha commented Feb 17, 2020

@nickboldt
Is it still relevant?

@tolusha tolusha added this to the Backlog - Deploy milestone Feb 17, 2020
@tolusha tolusha added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed severity/P1 Has a major impact to usage or development of the system. labels Feb 17, 2020
@tolusha tolusha removed this from the Backlog - Deploy milestone Feb 17, 2020
@tolusha tolusha removed the area/install Issues related to installation, including offline/air gap and initial setup label Feb 17, 2020
@tolusha tolusha removed the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Mar 20, 2020
@tolusha tolusha closed this as completed Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nickboldt @tolusha @che-bot