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

"Upgrade history" feature to be implemented #194

Closed
deenav opened this issue May 21, 2019 · 2 comments
Closed

"Upgrade history" feature to be implemented #194

deenav opened this issue May 21, 2019 · 2 comments
Assignees
@pbelgundi
Labels
area/upgrade Impacts upgrade feature in operator kind/feature New feature priority/P3 No direct impact to applications, e.g., typos in documentation or log messages status/work-in-progress PR work is in progress; do not merge version 0.4.0 Issue with Operator 0.4.0

Comments

@deenav
Copy link

deenav commented May 21, 2019

With current verison 0.4.0-rc1 of Pravega upgrade process, there is no way to find the upgrade history or upgrade path other than searching it from logs.

Only during the upgrade there are status like Current Version and Target Version shown from kubectl describe PravegaCluster output.

But after upgrade completion kubectl describe PravegaCluster only shows Version field, with that we can not determine the Previous Version from where the Pravega got upgraded.

And over the period of time if a customer/user performs multiple upgrades of Pravega then there should be a way to keep track of it.

So, it would be good to have some command readily available to check the previous version or upgrade path.
@Tristan1900
Copy link
Member

This probably could be done by keeping history in Pravega manifest annotation field. K8s uses the same way to keep track of the rollout history of deployment. Ref.

@Tristan1900 Tristan1900 added the kind/feature New feature label May 21, 2019
@adrianmo adrianmo added status/needs-investigation Further investigation is required priority/P3 No direct impact to applications, e.g., typos in documentation or log messages labels May 30, 2019
@pbelgundi pbelgundi added the version 0.4.0 Issue with Operator 0.4.0 label Jul 2, 2019
@pbelgundi pbelgundi self-assigned this Sep 13, 2019
@pbelgundi
Copy link
Contributor

pbelgundi commented Sep 13, 2019 •
edited
Loading

Provided via versionHistory field in Rollback PR:
#255

@pbelgundi pbelgundi added area/upgrade Impacts upgrade feature in operator status/work-in-progress PR work is in progress; do not merge and removed status/needs-investigation Further investigation is required labels Sep 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pbelgundi pbelgundi

Labels
area/upgrade Impacts upgrade feature in operator kind/feature New feature priority/P3 No direct impact to applications, e.g., typos in documentation or log messages status/work-in-progress PR work is in progress; do not merge version 0.4.0 Issue with Operator 0.4.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@adrianmo @Tristan1900 @deenav @pbelgundi