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: server:update should provide an ability to update Che Server configuration #14974

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

chectl: server:update should provide an ability to update Che Server configuration #14974

sleshchenko opened this issue Oct 24, 2019 · 2 comments
Assignees
@AndrienkoAleksandr
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.
Milestone
7.21

Comments

@sleshchenko
Copy link
Member

Is your enhancement related to a problem? Please describe.

Currently, server:update only applied installer resources and update images version.
It would be nice if it also allows user to update Che Server configuration with different arguments that user is able to use for server:start, like --multiuser, --tls, --self-signed-cert, etc.
@sleshchenko sleshchenko added kind/enhancement A feature request - must adhere to the feature request template. area/chectl Issues related to chectl, the CLI of Che labels Oct 24, 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 24, 2019
@tsmaeder
Copy link
Contributor

Does updating those properties now require an uninstall/install of che or can they be changed in the kubernetes config?

@tsmaeder tsmaeder added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Oct 28, 2019
@sleshchenko
Copy link
Member Author

Does updating those properties now require an uninstall/install of che or can they be changed in the kubernetes config?

I believe changing kubernetes objects is enough. The only config we should not allow to reconfigure - --multiuser since data will be lost and it may be not something a user expects to see.

@benoitf benoitf 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 Nov 20, 2019
@tolusha tolusha added team/deploy and removed status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Feb 17, 2020
@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. team/deploy labels May 6, 2020
@tolusha tolusha modified the milestone: Backlog - Deploy May 6, 2020
@tolusha tolusha modified the milestones: Backlog - Deploy, 7.21 Sep 29, 2020
@tolusha tolusha mentioned this issue Oct 1, 2020
Closed
50 tasks
@AndrienkoAleksandr AndrienkoAleksandr self-assigned this Oct 9, 2020
@AndrienkoAleksandr AndrienkoAleksandr mentioned this issue Oct 12, 2020
Merged
9 tasks
@tolusha tolusha closed this as completed Oct 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AndrienkoAleksandr AndrienkoAleksandr

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
7.21
Development

No branches or pull requests
6 participants
@benoitf @tolusha @sleshchenko @AndrienkoAleksandr @tsmaeder @che-bot