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

Che devfile and plugin registry in-repo templates should use Deployments on OpenShift #20133

Closed
amisevsk opened this issue Jul 15, 2021 · 7 comments
Assignees
Labels
area/devfile-registry area/plugin-registry kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@amisevsk
Copy link
Contributor

Is your task related to a problem? Please describe.

The Che Devfile and Plugin registry repos contain a deploy dir that can be used for easily deploying the registries on OpenShift. However, the OpenShift templates in these directories use DeploymentConfigs instead of Deployments to support the registry.

Describe the solution you'd like

Use Deployments for registries

Describe alternatives you've considered

Keep doing what we're doing

Additional context

The OpenShift docs recommend using Deployments unless DeploymentConfig-specific features are required.

@amisevsk amisevsk added kind/task Internal things, technical debt, and to-do tasks to be performed. area/devfile-registry area/plugin-registry labels Jul 15, 2021
@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 Jul 15, 2021
@l0rd l0rd added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 15, 2021
@che-bot
Copy link
Contributor

che-bot commented Jan 11, 2022

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 Jan 11, 2022
@amisevsk
Copy link
Contributor Author

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 11, 2022
@che-bot
Copy link
Contributor

che-bot commented Jul 10, 2022

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 Jul 10, 2022
@che-bot che-bot closed this as completed Jul 17, 2022
@svor
Copy link
Contributor

svor commented Jul 18, 2022

/remove-lifecycle stale

@svor svor reopened this Jul 18, 2022
@svor svor removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 18, 2022
@che-bot
Copy link
Contributor

che-bot commented Jan 14, 2023

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 Jan 14, 2023
@svor svor removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 16, 2023
@che-bot
Copy link
Contributor

che-bot commented Jul 15, 2023

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 Jul 15, 2023
@svor
Copy link
Contributor

svor commented Jul 17, 2023

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2023
@amisevsk amisevsk added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 17, 2023
@svor svor self-assigned this Sep 27, 2023
@ibuziuk ibuziuk moved this to 📅 Planned in Eclipse Che Team A Backlog Sep 27, 2023
@svor svor moved this from 📅 Planned to 🚧 In Progress in Eclipse Che Team A Backlog Oct 9, 2023
@svor svor moved this from 🚧 In Progress to Ready for Review in Eclipse Che Team A Backlog Oct 10, 2023
@svor svor closed this as completed Oct 12, 2023
@svor svor moved this from Ready for Review to ✅ Done in Eclipse Che Team A Backlog Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-registry area/plugin-registry kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants