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

[spike] Design a solution for updating the exsiting instances of Eclipse Che and migrating them to the 'eclipse-che' namespace #17414

Closed
ibuziuk opened this issue Jul 15, 2020 · 1 comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/install Issues related to installation, including offline/air gap and initial setup kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jul 15, 2020

Is your task related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

@ibuziuk ibuziuk added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. team/hosted-che labels Jul 15, 2020
@ibuziuk ibuziuk changed the title design a solution for updating the exsiting instances of Eclipse Che and migrating them to the 'eclipse-che' namespace [spike] Design a solution for updating the exsiting instances of Eclipse Che and migrating them to the 'eclipse-che' namespace Jul 15, 2020
@ibuziuk ibuziuk added this to the 7.17 milestone Jul 15, 2020
@l0rd l0rd added area/install Issues related to installation, including offline/air gap and initial setup area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator labels Jul 29, 2020
@ibuziuk ibuziuk removed this from the 7.17 milestone Aug 5, 2020
@che-bot
Copy link
Contributor

che-bot commented Feb 4, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 4, 2021
@che-bot che-bot closed this as completed Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/install Issues related to installation, including offline/air gap and initial setup kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants