Skip to content

Commit 29461b2

Browse files
authored
merge(#1279): prepared chart 0.21.0
Prepared Cadence chart for release 0.21.0 #1279
2 parents 0919186 + 9bebcfc commit 29461b2

File tree

2 files changed

+85
-1
lines changed

2 files changed

+85
-1
lines changed

cadence/Chart.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
name: cadence
2-
version: 0.20.2
2+
version: 0.21.0
33
appVersion: 0.21.3
44
description: Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
55
icon: https://raw.githubusercontent.com/uber/cadence-web/master/client/assets/logo.svg

cadence/README.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,90 @@ $ helm install --name my-release --namespace cadence banzaicloud-stable/cadence
3333
> **Tip**: List all releases using `helm list`
3434
3535

36+
## Upgrading Chart
37+
38+
```console
39+
# Helm
40+
$ helm upgrade [RELEASE_NAME] banzaicloud-stable/cadence
41+
```
42+
43+
### From 0.20.x (or below) to 0.21.y (or above)
44+
45+
Version 0.21.0 extends the configuration interface by introducing
46+
`clusterMetadata` settings to the `values.yaml` in a backward incompatible
47+
manner with existing Cadence clusters.
48+
49+
To upgrade the Cadence deployment under **existing** Cadence clusters from
50+
version 0.20.x (or below) to 0.21.y (or above) you **MUST** set the existing
51+
cluster's configuration in the `values.yaml` file's
52+
`.server.config.clusterMetadata` section to be used for the upgrade.
53+
54+
#### Example configuration for upgrading from version 0.16.x (or below)
55+
56+
```yaml
57+
server:
58+
# ...
59+
config:
60+
clusterMetadata:
61+
enableGlobalDomain: true
62+
maximumClusterCount: 10
63+
masterClusterName: "active"
64+
currentClusterName: "active"
65+
clusterInformation:
66+
- name: active
67+
enabled: true
68+
```
69+
70+
#### Example configuration for upgrading from version 0.17.x
71+
72+
```yaml
73+
server:
74+
# ...
75+
config:
76+
clusterMetadata:
77+
enableGlobalDomain: true
78+
maximumClusterCount: 10
79+
masterClusterName: "master"
80+
currentClusterName: "master"
81+
clusterInformation:
82+
- name: master
83+
enabled: true
84+
```
85+
86+
#### Example configuration for upgrading from 0.18.x (or above), single Cadence cluster
87+
88+
```yaml
89+
server:
90+
# ...
91+
config:
92+
clusterMetadata:
93+
enableGlobalDomain: true
94+
maximumClusterCount: 10
95+
masterClusterName: "primary"
96+
currentClusterName: "primary"
97+
clusterInformation:
98+
- name: primary
99+
enabled: true
100+
```
101+
102+
#### Example configuration for upgrading from 0.18.x (or above), multiple Cadence clusters
103+
104+
```yaml
105+
server:
106+
# ...
107+
config:
108+
clusterMetadata:
109+
enableGlobalDomain: true
110+
maximumClusterCount: 10
111+
masterClusterName: "primary"
112+
currentClusterName: "primary" # "secondary" # Note: use the name of the Cadence cluster you are using on the cluster/namespace/release you are upgrading.
113+
clusterInformation:
114+
- name: primary
115+
enabled: true
116+
- name: secondary
117+
enabled: true
118+
```
119+
36120
## Uninstalling the Chart
37121
38122
To uninstall/delete the `my-release` deployment:

0 commit comments

Comments
 (0)