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

[chectl] Support helm installer for server:update command #14973

Closed
sleshchenko opened this issue Oct 24, 2019 · 3 comments
Closed

[chectl] Support helm installer for server:update command #14973

sleshchenko opened this issue Oct 24, 2019 · 3 comments
Labels
area/chectl Issues related to chectl, the CLI of Che kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.

Comments

@sleshchenko
Copy link
Member

Is your enhancement related to a problem? Please describe.

Support helm installer for server:update command.

Describe the solution you'd like

Support helm installer for server:update command.
The difficulty I see here: it's not clear how to handle values.
The easiest solution I see: user must specify exactly the same arguments that they specified during for server:start, like server:start --domain=myk8s.com --tls --multiuser.
Or maybe chectl is able to read values of deployed Che from deployed Helm Chart as application, maybe try to guess smart according to created k8s objects, like postgresq, TLS cert, etc.
@sleshchenko sleshchenko added the kind/enhancement A feature request - must adhere to the feature request template. label Oct 24, 2019
@sleshchenko sleshchenko added this to the Backlog - Dev Experience milestone Oct 24, 2019
@sleshchenko sleshchenko added the area/chectl Issues related to chectl, the CLI of Che label Oct 24, 2019
@tolusha tolusha removed this from the Backlog - Dev Experience milestone Feb 17, 2020
@tolusha tolusha added severity/P2 Has a minor but important impact to the usage or development of the system. team/deploy labels Feb 17, 2020
@sleshchenko sleshchenko mentioned this issue Apr 17, 2020
Closed
@tolusha tolusha added severity/P1 Has a major impact to usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels May 4, 2020
@che-bot
Copy link
Contributor

che-bot commented Jan 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 Jan 4, 2021
@tolusha tolusha added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 4, 2021
@anortef
Copy link

anortef commented Apr 7, 2021

Any news on this? because in the docs helm is the default for some platforms and this would be something nice to have.

@tolusha tolusha removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Aug 5, 2021
@tolusha
Copy link
Contributor

tolusha commented Nov 29, 2021

chectl doesn't support --installer helm anymore.
We introduced another Helm Charts [1] in [2]

[1] https://github.com/eclipse-che/che-operator/tree/main/helmcharts
[2] eclipse-che/che-operator#1184

@tolusha tolusha closed this as completed Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/chectl Issues related to chectl, the CLI of Che kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@anortef @tolusha @sleshchenko @che-bot