You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sh -x stackgres-k8s/ci/utils/update-version.sh "1.18.0-rc4"
29
+
sh -x stackgres-k8s/ci/utils/update-version.sh "1.18.0-rc5"
30
30
```
31
31
1. [ ] Update `CHANGELOG.md` (review commit messages to populate the changelog: `git log`)
32
-
1. [ ] Add 1.18.0-rc4 section in `doc/content/en/01-introduction/06-versions/_index.md` with values from `stackgres-k8s/src/common/src/main/resources/versions-1.18.properties`
32
+
1. [ ] Add 1.18.0-rc5 section in `doc/content/en/01-introduction/06-versions/_index.md` with values from `stackgres-k8s/src/common/src/main/resources/versions-1.18.properties`
33
33
1. [ ] Check the changes to ensure everything is correct before commit:
34
34
```
35
35
git diff
36
36
```
37
-
1. [ ] Commit changes with message `version: 1.18.0-rc4`:
37
+
1. [ ] Commit changes with message `version: 1.18.0-rc5`:
38
38
```
39
-
git commit -S -a -m "version: 1.18.0-rc4"
39
+
git commit -S -a -m "version: 1.18.0-rc5"
40
40
```
41
-
1. [ ] Push `release-1.18.0-rc4` branch:
41
+
1. [ ] Push `release-1.18.0-rc5` branch:
42
42
43
43
**This step requires at least one ARM instance with docker installed and a gitlab runner registered with the StackGres project. All this setup is already built in a template. The only action we need to do is scale up the auto-scaling group `sg-army-builder` auto scaling group.**
44
44
@@ -53,9 +53,9 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
1. [ ] Perform preflight for operator images (make each of them pass pass the index health check by opening each image project):
@@ -66,16 +66,16 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
66
66
67
67
```
68
68
cd stackgres-k8s/install/operator-sdk/openshift-certification/
69
-
STACKGRES_VERSION="1.18.0-rc4" IMAGE_TAG="$(git rev-parse --short=8 HEAD)" sh get-images.sh | grep -F quay.io/stackgres/ | sed 's#quay\.io/stackgres/#registry.gitlab.com/ongresinc/stackgres/stackgres/#' | xargs -I % sh preflight.sh %
69
+
STACKGRES_VERSION="1.18.0-rc5" IMAGE_TAG="$(git rev-parse --short=8 HEAD)" sh get-images.sh | grep -F quay.io/stackgres/ | sed 's#quay\.io/stackgres/#registry.gitlab.com/ongresinc/stackgres/stackgres/#' | xargs -I % sh preflight.sh %
70
70
```
71
71
72
-
1. [ ] Create tag `1.18.0-rc4`:
72
+
1. [ ] Create tag `1.18.0-rc5`:
73
73
```
74
-
git tag "1.18.0-rc4"
74
+
git tag "1.18.0-rc5"
75
75
```
76
-
1. [ ] Push tag `1.18.0-rc4` to the origin and wait for the pipeline to complete:
76
+
1. [ ] Push tag `1.18.0-rc5` to the origin and wait for the pipeline to complete:
77
77
```
78
-
git push origin "1.18.0-rc4"
78
+
git push origin "1.18.0-rc5"
79
79
```
80
80
1. [ ] After pipeline succeeded, scale down the ARM runners (or terminate the instance created with the script):
81
81
```
@@ -88,7 +88,7 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
88
88
89
89
```
90
90
cd stackgres-k8s/install/operator-sdk/openshift-certification/
91
-
STACKGRES_VERSION="1.18.0-rc4" IMAGE_TAG="1.18.0-rc4" sh get-images.sh | grep -F quay.io/stackgres/ | xargs -I % sh preflight.sh %
91
+
STACKGRES_VERSION="1.18.0-rc5" IMAGE_TAG="1.18.0-rc5" sh get-images.sh | grep -F quay.io/stackgres/ | xargs -I % sh preflight.sh %
92
92
```
93
93
1. [ ] Create PR on Red Hat Certified Operators (wait for its completion):
94
94
> File that export environment variable `FORK_GIT_URL` with the git URL (make sure user can perform push on such URL) of the project that forks project `https://github.com/redhat-openshift-ecosystem/redhat-marketplace-operators` must be specified in POSIX shell script with path `~/.stackgres/operator-bundle-red-hat-certified-config`
@@ -101,15 +101,15 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
101
101
> The pipeline may fail and some changes to the operator bunle may be required. Perform such changes only on path `stackgres-k8s/install/operator-sdk/stackgres-operator/` on a separate branch:
> When PR is merged create a MR to `main-1.18.0-rc4` branch.
112
+
> When PR is merged create a MR to `main-1.18.0-rc5` branch.
113
113
1. [ ] Create PR on Red Hat Marketplace Operators (wait for its completion):
114
114
> File that export environment variable `FORK_GIT_URL` with the git URL (make sure user can perform push on such URL) of the project that forks project `https://github.com/redhat-openshift-ecosystem/certified-operators` must be specified in POSIX shell script with path `~/.stackgres/operator-bundle-red-hat-certified-config`
115
115
@@ -121,15 +121,15 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
121
121
> The pipeline may fail and some changes to the operator bunle may be required. Perform such changes only on path `stackgres-k8s/install/operator-sdk/stackgres-operator/` on a separate branch:
> When PR is merged create a MR to `main-1.18.0-rc4` branch.
132
+
> When PR is merged create a MR to `main-1.18.0-rc5` branch.
133
133
1. [ ] Create PR on Red Hat Community Operators (wait for its completion):
134
134
> File that export environment variable `FORK_GIT_URL` with the git URL (make sure user can perform push on such URL) of the project that forks project `https://github.com/redhat-openshift-ecosystem/community-operators-prod` must be specified in POSIX shell script with path `~/.stackgres/operator-bundle-red-hat-community-config`
135
135
@@ -141,15 +141,15 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
141
141
> The pipeline may fail and some changes to the operator bunle may be required. Perform such changes only on path `stackgres-k8s/install/operator-sdk/stackgres-operator/` on a separate branch:
> When PR is merged create a MR to `main-1.18.0-rc4` branch.
152
+
> When PR is merged create a MR to `main-1.18.0-rc5` branch.
153
153
1. [ ] Create PR on OperatorHub (wait for its completion):
154
154
> File that export environment variable `FORK_GIT_URL` with the git URL (make sure user can perform push on such URL) of the project that forks project `https://github.com/k8s-operatorhub/community-operators` must be specified in POSIX shell script with path `~/.stackgres/operator-bundle-operatorhub-config`
155
155
@@ -161,37 +161,37 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
161
161
> The pipeline may fail and some changes to the operator bunle may be required. Perform such changes only on path `stackgres-k8s/install/operator-sdk/stackgres-operator/` on a separate branch:
> When PR is merged create a MR to `main-1.18.0-rc4` branch.
173
-
1. [ ] Edit the [release notes of tag 1.18.0-rc4](https://gitlab.com/ongresinc/stackgres/-/releases/new?tag_name=1.18.0-rc4) by Copying and Pasting `CHANGELOG.md` section for version `1.18.0-rc4` (GitLab)
174
-
1. [ ] Merge local branch `release-1.18.0-rc4` into `main-1.18`:
172
+
> When PR is merged create a MR to `main-1.18.0-rc5` branch.
173
+
1. [ ] Edit the [release notes of tag 1.18.0-rc5](https://gitlab.com/ongresinc/stackgres/-/releases/new?tag_name=1.18.0-rc5) by Copying and Pasting `CHANGELOG.md` section for version `1.18.0-rc5` (GitLab)
174
+
1. [ ] Merge local branch `release-1.18.0-rc5` into `main-1.18`:
1. [ ] Merge branch `main-1.18` into `merge-1.18.0-rc4`:
188
+
1. [ ] Merge branch `main-1.18` into `merge-1.18.0-rc5`:
189
189
```
190
190
git merge "main-1.18"
191
191
```
192
-
1. [ ] Push `merge-1.18.0-rc4` to origin, create the merge request to merge it into `main` and wait for the pipeline to complete fixing any encountered issues:
192
+
1. [ ] Push `merge-1.18.0-rc5` to origin, create the merge request to merge it into `main` and wait for the pipeline to complete fixing any encountered issues:
193
193
```
194
-
git push origin "merge-1.18.0-rc4"
194
+
git push origin "merge-1.18.0-rc5"
195
195
```
196
196
197
197
# Deploy Web
@@ -202,10 +202,10 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
202
202
git checkout development && git pull
203
203
```
204
204
1. [ ] Edit `.gitlab-ci.yml`:
205
-
* Change `STACKGRES_FULL_VERSIONS` by setting `1.18.0-rc4` as the first value.
206
-
1. [ ] Commit changes with message `version: 1.18.0-rc4`:
205
+
* Change `STACKGRES_FULL_VERSIONS` by setting `1.18.0-rc5` as the first value.
206
+
1. [ ] Commit changes with message `version: 1.18.0-rc5`:
207
207
```
208
-
git commit -a -m 'version: 1.18.0-rc4'
208
+
git commit -a -m 'version: 1.18.0-rc5'
209
209
```
210
210
1. [ ] Push development to origin:
211
211
```
@@ -216,17 +216,17 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
@@ -238,11 +238,11 @@ sh stackgres-k8s/ci/utils/generate-release-template.sh $VERSION
238
238
# Changelog
239
239
240
240
~~~
241
-
# :rocket: Release 1.18.0-rc4 (${DATE})
241
+
# :rocket: Release 1.18.0-rc5 (${DATE})
242
242
243
243
## :notepad_spiral: NOTES
244
244
245
-
StackGres 1.18.0-rc4 is out! :confetti_ball: :champagne:
245
+
StackGres 1.18.0-rc5 is out! :confetti_ball: :champagne:
246
246
247
247
So, what you are waiting for to try this release and have a look to the future of StackGres!
248
248
@@ -273,15 +273,15 @@ To upgrade from a previous installation of the StackGres operator's helm chart y
273
273
274
274
To upgrade StackGres operator's (upgrade only works starting from 1.1 version or above) helm chart issue the following commands (replace namespace and release name if you used something different):
> IMPORTANT: This release is incompatible with previous `alpha` or `beta` versions. Upgrading from those versions will require uninstalling completely StackGres including all clusters and StackGres CRDs (those in `stackgres.io` group) first.
279
279
280
280
Thank you for all the issues created, ideas, and code contributions by the StackGres Community!
281
281
282
-
## :twisted_rightwards_arrows: [FULL LIST OF COMMITS](https://gitlab.com/ongresinc/stackgres/-/commits/1.18.0-rc4)
282
+
## :twisted_rightwards_arrows: [FULL LIST OF COMMITS](https://gitlab.com/ongresinc/stackgres/-/commits/1.18.0-rc5)
Copy file name to clipboardExpand all lines: CHANGELOG.md
+71Lines changed: 71 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,74 @@
1
+
# :rocket: Release 1.18.0-rc4 (2025-11-24)
2
+
3
+
## :notepad_spiral: NOTES
4
+
5
+
StackGres 1.18.0-rc4 is out! :confetti_ball::champagne:
6
+
7
+
> This release candidate fixes a few issues present in 1.18.0-rc3
8
+
9
+
Among other features this release will allow you to upgrade your clusters using a strategy and with a renewed rollout implementation that no longer relies on Jobs but is handled directly by the operator. You can still rely on SGDbOps to perform restarts, security upgrades and minor version upgrades operations or configure the clusters to preform them in an automatic fashion.
10
+
11
+
Another important change is the ability to set the version of your SGCluster or SGShardedCluster directly in the cluster resource. The final Postgres version (and the final extensions versions too) will no longer be changed by the operator, instead it will be set in the status and will be updated by the operator. This change will allow a much better integration with DevOps tools!
12
+
13
+
So, what you are waiting for! Upgrade now and have a look at the future of StackGres!
* PersistentVolumeClaim are not cleaned up after cluster deletion
44
+
* PodMonitor is continuously patched and not removed when requested by configuration
45
+
* Kubernetes cluster using IPv6 breaks replication initialization mode `FromReplica`
46
+
* Use target cluster labels for cleanup after major upgrade completed
47
+
48
+
## Web Console
49
+
50
+
* Allow to unset cronSchedule and backup paths for clusters and sharded clusters
51
+
* Remove default SGScript on clone
52
+
53
+
## :construction: KNOWN ISSUES
54
+
55
+
* Backups may be restored with inconsistencies when performed with a Postgres instance running on a different architecture ([#1539](https://gitlab.com/ongresinc/stackgres/-/issues/1539))
56
+
57
+
## :up: UPGRADE
58
+
59
+
To upgrade from a previous installation of the StackGres operator's helm chart you will have to upgrade the helm chart release.
60
+
For more detailed information please refer to [our documentation](https://stackgres.io/doc/latest/install/helm/upgrade/#upgrade-operator).
61
+
62
+
To upgrade StackGres operator's (upgrade only works starting from 1.1 version or above) helm chart issue the following commands (replace namespace and release name if you used something different):
> IMPORTANT: This release is incompatible with previous `alpha` or `beta` versions. Upgrading from those versions will require uninstalling completely StackGres including all clusters and StackGres CRDs (those in `stackgres.io` group) first.
67
+
68
+
Thank you for all the issues created, ideas, and code contributions by the StackGres Community!
69
+
70
+
## :twisted_rightwards_arrows:[FULL LIST OF COMMITS](https://gitlab.com/ongresinc/stackgres/-/commits/1.18.0-rc4)
0 commit comments