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

Add support for versioning and publishing of helm charts for supporting helm upgrades #388

Closed
pbelgundi opened this issue May 6, 2020 · 0 comments · Fixed by #409
Closed
Assignees
Labels
area/charts Issue related to Operator or Pravega Helm chart Pravega 0.8.0 Fix by pravega 0.8.0 priority/P1 Recoverable error, functionality/performance impaired but not lost, no permanent damage

Comments

@pbelgundi
Copy link
Contributor

Description

Currently our helm charts are not versioned or published.
There is no conscious effort to maintain upgrade compatibility in charts.

Importance

must-have

Location

https://github.com/pravega/pravega-operator/tree/master/charts

@pbelgundi pbelgundi added priority/P1 Recoverable error, functionality/performance impaired but not lost, no permanent damage status/needs-investigation Further investigation is required area/charts Issue related to Operator or Pravega Helm chart Pravega 0.8.0 Fix by pravega 0.8.0 labels May 6, 2020
@pbelgundi pbelgundi changed the title Add support for helm V3 and helm upgrades Add support for versioning and publishing of helm charts for supporting helm upgrades May 26, 2020
@SrishT SrishT assigned SrishT and unassigned anishakj Jun 24, 2020
@Ranganaths8 Ranganaths8 removed the status/needs-investigation Further investigation is required label Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/charts Issue related to Operator or Pravega Helm chart Pravega 0.8.0 Fix by pravega 0.8.0 priority/P1 Recoverable error, functionality/performance impaired but not lost, no permanent damage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants