bump to v1.9.0 - #2177
bump to v1.9.0#2177
Conversation
FxKu
commented
Jan 17, 2023
- bump operator image in deployment manifest
- bump logical backup default image
- update version in helm charts and create new packages
- drop v1.6.x tgz packages from helm folders
| registry: registry.opensource.zalan.do | ||
| repository: acid/postgres-operator-ui | ||
| tag: v1.8.2 | ||
| tag: v1.9.0 |
There was a problem hiding this comment.
@FxKu do you mind that master branch should contains latest tag and specific version tag should be present inside the chart archive only. Otherwise is not possible to install chart from the current master in the development (with some modifications manifests values).
wdyt about it?
There was a problem hiding this comment.
well my idea is to tag a release as soon as this PR is merged :)
but we can also think of changing it to latest so that issues like #2153 stop popping up.
There was a problem hiding this comment.
Yes, indeed. We could always have the latest tag and imagePullPolicy: Always on the master and create release script to automate this operation.
There was a problem hiding this comment.
Keep in mind! The default imagePullPolicy always pulls the :latest tag! As such, it should not be specified for this usecase.
https://kubernetes.io/docs/concepts/containers/images/#imagepullpolicy-defaulting
There was a problem hiding this comment.
@katlol I know about it, thank you. But for this case, it's better to specified it to simplify release scripts for helm chart if this approach could be implemented.
|
Before that release it would be realy nice to add an ci step, which pushes the chart to some real helm repo. This can be achived very easily by using: https://github.com/helm/chart-releaser-action |
|
@monotek we will do it for the next release when we have CI for multi-arch operator image |
|
👍 |
1 similar comment
|
👍 |