@serve.zone/appstore 32.6.0 → 32.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/apps/cloudly/app.json +2 -2
- package/apps/cloudly/versions/1.7.0/config.json +173 -0
- package/apps/cloudly/versions/1.8.0/config.json +173 -0
- package/appstore.json +1 -1
- package/changelog.md +20 -0
- package/dist_ts_client/data.generated.js +352 -4
- package/package.json +1 -1
- package/readme.md +2 -2
- package/ts_client/data.generated.ts +351 -3
package/apps/cloudly/app.json
CHANGED
|
@@ -4,8 +4,8 @@
|
|
|
4
4
|
"description": "Multi-node serve.zone control plane for clusters, workload services, domains, and deployments.",
|
|
5
5
|
"category": "Dev Tools",
|
|
6
6
|
"iconName": "server",
|
|
7
|
-
"latestVersion": "1.
|
|
8
|
-
"versions": ["1.0.0", "1.1.0", "1.1.1", "1.1.2", "1.1.3", "1.1.4", "1.1.5", "1.1.6", "1.1.7", "1.1.8", "1.1.9", "1.1.10", "1.2.0", "1.2.1", "1.3.0", "1.4.0", "1.5.0", "1.6.0"],
|
|
7
|
+
"latestVersion": "1.8.0",
|
|
8
|
+
"versions": ["1.0.0", "1.1.0", "1.1.1", "1.1.2", "1.1.3", "1.1.4", "1.1.5", "1.1.6", "1.1.7", "1.1.8", "1.1.9", "1.1.10", "1.2.0", "1.2.1", "1.3.0", "1.4.0", "1.5.0", "1.6.0", "1.7.0", "1.8.0"],
|
|
9
9
|
"maintainer": "serve.zone",
|
|
10
10
|
"links": {
|
|
11
11
|
"Source": "https://code.foss.global/serve.zone/cloudly",
|
|
@@ -0,0 +1,173 @@
|
|
|
1
|
+
{
|
|
2
|
+
"image": "code.foss.global/serve.zone/cloudly@sha256:f4f88f0c3765d1b129fa4f3ff68438958e55d4fad598393fb0c686261e46c7ed",
|
|
3
|
+
"targetPorts": [
|
|
4
|
+
{
|
|
5
|
+
"name": "web",
|
|
6
|
+
"port": 3000,
|
|
7
|
+
"protocol": "http",
|
|
8
|
+
"default": true
|
|
9
|
+
}
|
|
10
|
+
],
|
|
11
|
+
"envVars": [
|
|
12
|
+
{
|
|
13
|
+
"key": "SERVEZONE_ENVIRONMENT",
|
|
14
|
+
"value": "production",
|
|
15
|
+
"description": "Cloudly runtime environment.",
|
|
16
|
+
"required": true
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"key": "SERVEZONE_PUBLIC_ORIGIN",
|
|
20
|
+
"value": "https://${SERVICE_DOMAIN}",
|
|
21
|
+
"description": "Canonical public Cloudly origin including protocol and optional public port.",
|
|
22
|
+
"required": true
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"key": "SERVEZONE_LISTENPORT",
|
|
26
|
+
"value": "3000",
|
|
27
|
+
"description": "Internal Cloudly HTTP port inside the container.",
|
|
28
|
+
"required": true
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"key": "SERVEZONE_SSLMODE",
|
|
32
|
+
"value": "external",
|
|
33
|
+
"description": "Use external TLS termination through Onebox or dcrouter.",
|
|
34
|
+
"required": true
|
|
35
|
+
},
|
|
36
|
+
{
|
|
37
|
+
"key": "SERVEZONE_SECRET_KEYRING_PATH",
|
|
38
|
+
"value": "/run/secrets/cloudly-secrets-v2-keyring.json",
|
|
39
|
+
"description": "Path to the Cloudly Secrets v2 keyring mounted by Onebox; the keyring value is never placed in the public environment.",
|
|
40
|
+
"required": true
|
|
41
|
+
},
|
|
42
|
+
{
|
|
43
|
+
"key": "SERVEZONE_SECRET_KEYRING_FILE",
|
|
44
|
+
"description": "Existing Cloudly Secrets v2 keyring. Onebox stores it encrypted and mounts it only as a root-readable file; retain the existing keyring when upgrading.",
|
|
45
|
+
"required": true,
|
|
46
|
+
"secret": true,
|
|
47
|
+
"delivery": {
|
|
48
|
+
"type": "file",
|
|
49
|
+
"targetPath": "/run/secrets/cloudly-secrets-v2-keyring.json",
|
|
50
|
+
"uid": 0,
|
|
51
|
+
"gid": 0,
|
|
52
|
+
"mode": 256
|
|
53
|
+
}
|
|
54
|
+
},
|
|
55
|
+
{
|
|
56
|
+
"key": "SERVEZONE_WORKLOADINIT_APPROVAL_PATH",
|
|
57
|
+
"value": "/run/secrets/cloudly-workloadinit-approval.json",
|
|
58
|
+
"description": "Private WorkloadInit release-approval artifact mounted by Onebox for Coreflow secret-runtime registration.",
|
|
59
|
+
"required": true
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"key": "SERVEZONE_WORKLOADINIT_APPROVAL_FILE",
|
|
63
|
+
"description": "Operator-approved WorkloadInit release authority. Onebox stores it encrypted and mounts it only as a root-readable file.",
|
|
64
|
+
"required": true,
|
|
65
|
+
"secret": true,
|
|
66
|
+
"delivery": {
|
|
67
|
+
"type": "file",
|
|
68
|
+
"targetPath": "/run/secrets/cloudly-workloadinit-approval.json",
|
|
69
|
+
"uid": 0,
|
|
70
|
+
"gid": 0,
|
|
71
|
+
"mode": 256
|
|
72
|
+
}
|
|
73
|
+
},
|
|
74
|
+
{
|
|
75
|
+
"key": "MONGODB_URL",
|
|
76
|
+
"value": "${MONGODB_URI}",
|
|
77
|
+
"description": "Authenticated MongoDB wire-protocol URL provisioned by Onebox Corestore.",
|
|
78
|
+
"required": true
|
|
79
|
+
},
|
|
80
|
+
{
|
|
81
|
+
"key": "MONGODB_NAME",
|
|
82
|
+
"value": "${MONGODB_DATABASE}",
|
|
83
|
+
"description": "MongoDB wire-protocol database name provisioned by Onebox Corestore.",
|
|
84
|
+
"required": true
|
|
85
|
+
},
|
|
86
|
+
{
|
|
87
|
+
"key": "MONGODB_USER",
|
|
88
|
+
"value": "${MONGODB_USERNAME}",
|
|
89
|
+
"description": "MongoDB wire-protocol username provisioned by Onebox Corestore.",
|
|
90
|
+
"required": true
|
|
91
|
+
},
|
|
92
|
+
{
|
|
93
|
+
"key": "MONGODB_PASS",
|
|
94
|
+
"value": "${MONGODB_PASSWORD}",
|
|
95
|
+
"description": "MongoDB wire-protocol password provisioned by Onebox Corestore.",
|
|
96
|
+
"required": true
|
|
97
|
+
},
|
|
98
|
+
{
|
|
99
|
+
"key": "S3_ENDPOINT",
|
|
100
|
+
"value": "onebox-corestore",
|
|
101
|
+
"description": "S3 endpoint host provisioned by Onebox Corestore.",
|
|
102
|
+
"required": true
|
|
103
|
+
},
|
|
104
|
+
{
|
|
105
|
+
"key": "S3_PORT",
|
|
106
|
+
"value": "9000",
|
|
107
|
+
"description": "S3 endpoint port provisioned by Onebox Corestore.",
|
|
108
|
+
"required": true
|
|
109
|
+
},
|
|
110
|
+
{
|
|
111
|
+
"key": "S3_USESSL",
|
|
112
|
+
"value": "false",
|
|
113
|
+
"description": "Use plain HTTP for internal Corestore S3 traffic on the Onebox network.",
|
|
114
|
+
"required": true
|
|
115
|
+
},
|
|
116
|
+
{
|
|
117
|
+
"key": "S3_BUCKET",
|
|
118
|
+
"value": "${S3_BUCKET}",
|
|
119
|
+
"description": "S3 bucket provisioned by Onebox Corestore for Cloudly's registry.",
|
|
120
|
+
"required": true
|
|
121
|
+
},
|
|
122
|
+
{
|
|
123
|
+
"key": "S3_ACCESSKEY",
|
|
124
|
+
"value": "${S3_ACCESS_KEY}",
|
|
125
|
+
"description": "S3 access key provisioned by Onebox Corestore.",
|
|
126
|
+
"required": true
|
|
127
|
+
},
|
|
128
|
+
{
|
|
129
|
+
"key": "S3_SECRETKEY",
|
|
130
|
+
"value": "${S3_SECRET_KEY}",
|
|
131
|
+
"description": "S3 secret key provisioned by Onebox Corestore.",
|
|
132
|
+
"required": true
|
|
133
|
+
}
|
|
134
|
+
],
|
|
135
|
+
"platformRequirements": {
|
|
136
|
+
"mongodb": true,
|
|
137
|
+
"s3": true
|
|
138
|
+
},
|
|
139
|
+
"platformOidc": {
|
|
140
|
+
"redirectPath": "/auth/oidc/callback",
|
|
141
|
+
"roles": [
|
|
142
|
+
{
|
|
143
|
+
"id": "admin",
|
|
144
|
+
"label": "Administrator",
|
|
145
|
+
"description": "Full Cloudly administration for this hosted instance."
|
|
146
|
+
},
|
|
147
|
+
{
|
|
148
|
+
"id": "user",
|
|
149
|
+
"label": "User",
|
|
150
|
+
"description": "Standard authenticated Cloudly access for this hosted instance."
|
|
151
|
+
}
|
|
152
|
+
],
|
|
153
|
+
"environmentVariables": {
|
|
154
|
+
"issuerUrl": "SERVEZONE_PLATFORM_OIDC_ISSUER",
|
|
155
|
+
"clientId": "SERVEZONE_PLATFORM_OIDC_CLIENT_ID",
|
|
156
|
+
"clientSecret": "SERVEZONE_PLATFORM_OIDC_CLIENT_SECRET",
|
|
157
|
+
"redirectUri": "SERVEZONE_PLATFORM_OIDC_REDIRECT_URI",
|
|
158
|
+
"audience": "SERVEZONE_PLATFORM_OIDC_AUDIENCE"
|
|
159
|
+
},
|
|
160
|
+
"clientAuthenticationMethod": "client_secret_basic"
|
|
161
|
+
},
|
|
162
|
+
"minOneboxVersion": "32.4.0",
|
|
163
|
+
"changelog": "Move Cloudly to 33.4.0, a feature release over 33.3.0: setServicePublishedPorts accepts a contiguous published-port range through hostPortEnd, each host port to the same inside port, and same-port outbound through symmetric: true, so a SIP router can publish udp 20000-20200 and answer from the ports it listens on. Entries of one protocol never overlap and cover at most 1024 ports in 64 entries; a range onto other inside ports, hostIp and an overlap are refused, and a symmetric entry owns its inside ports, so another entry of the same protocol publishing to any of them is refused published-port-symmetric-inside-overlap. A symmetric entry needs public egress: published-port-symmetric-without-egress refuses it on a published-port write and refuses clearing egress under it on an egress write. New handoff leases translate outbound flows only into the SNAT band 49152-65535, whose ports are refused published-port-reserved; a leased handoff is immutable, so a node keeps its 1024-65535 lease until its router is re-created. The service runtime producer refuses an attached spec whose policy document, written before these rules, holds a reserved port or a symmetric port without egress. A service network policy write for a service whose deletion has begun is refused service-deleting. Cluster ingress port routes, HTTP routes and inbound mail targets are authorized by a range that covers their port, while an edge (dcrouter) route stays one route per port. A projection carrying a range or a symmetric entry is withheld from a Pallet node whose session states a release below interfaces 32.31.0, or none: its compilation reports node-contract-behind and the node keeps its current head, so ranges and symmetric entries take effect on a node only once it runs a Pallet release built on interfaces 32.31.0 or later. Two entries claiming one port of one node are withheld as published-port-conflict. The runtime contract is unchanged from 1.6.0 and requires Onebox 32.4.0. From 1.6.0, startup runs the forward-only data migration from 0.21.0 to 0.22.0 through the step runtime-session-protocol-offer, which states protocol: null on every Pallet session row recorded before Cloudly stored the protocol offer its node stated, so such a node counts as unrecorded until it registers again; stop Cloudly and take a verified backup before upgrading, because the step has no inverse and rollback requires a full restore. From 1.5.0 the same step runs, and the service network egress of Cloudly 33.3.0 applies too: an administrator sets a service's network egress with setServiceNetworkEgress, which states whether the service's attached workloads reach the public internet and which platform endpoints of the protected authority they reach, and reads it with getServiceNetworkEgress; a workload whose enabled database or object-storage binding sits on a node whose Corestore endpoint its network does not select is refused database-endpoint-unselected or objectstorage-endpoint-unselected, and a replica already running keeps running while its target reports the refusal, so grant the endpoint through the service's egress before such a workload is placed again; the default runtime spec of a new service probes its process instead of its first TCP target port. From 1.4.0 the same step runs, and the gateway admin bootstrap of Cloudly 33.2.0 applies too: an administrator hands Cloudly a dcrouter admin token once through bootstrapExternalGatewayCredential or servezone gateway bootstrap, from which Cloudly provisions and stores its own gateway-client credential; a first enrollment turns admin-bootstrap-required, a gateway settings change the held credential cannot carry is staged, a runtime network address plan out of its canonical order is refused plan-unsorted, and a relay naming a node Cloudly does not hold is refused relay-node-unknown: roll out Cloudly 33.4.0 first, then Coreflow 33.2.0, which recognises the relay-node-unknown refusal. From 1.3.0 the same step runs, and the per-node database endpoint of Cloudly 33.1.0 applies too: roll out Cloudly 33.4.0 first, then Coreflow 33.2.0 (33.1.0 at minimum), then Corestore 33.0.0, and set every node's Corestore database endpoint with setClusterNodeCorestoreDatabaseEndpoint, because a database binding on a node without one is not granted and its service is refused database-endpoint-missing, and existing database bindings answer no credential material until they are granted again for the endpoint. From 1.2.1 or earlier, startup runs the forward-only data migration from 0.20.0 to 0.21.0 through the step retire-cluster-relay-acme and then the step runtime-session-protocol-offer to 0.22.0; retire-cluster-relay-acme drops the relay certificate and DNS collections of Cloudly's retired Cloudflare and Let's Encrypt integration and logs every relay name whose A record Cloudly had written at Cloudflare: remove each such record at the provider. A cluster relay then requires a dcrouter that advertises dns.clientRecords and certificates.exactIssuance, SERVEZONE_SSLMODE=letsencrypt is refused (this template keeps external), and the typed API changes as the Breaking Changes of the Cloudly 33.0.0 changelog list; review them, stop Cloudly and take a verified backup before upgrading, because the 32.9 image refuses the migrated data and rollback requires a full restore. The upgrade is marked breaking, migration-required, backup-before-upgrade and manual-review because these flags are read from the target version alone, every upgrade from 1.6.0 or earlier runs the 0.21.0 to 0.22.0 step, and an upgrade from 1.2.1 or earlier still runs the migration from 0.20.0 on this image as well. An installation on 1.1.10 or earlier also runs the 1.2.0 steps first, from 0.10.0, and requires completed Secrets v2 cutover retirement. Preserve existing user and storage identities, OIDC bindings, the encrypted keyring and WorkloadInit approval as dedicated root-readable files.",
|
|
164
|
+
"breaking": true,
|
|
165
|
+
"requiresManualReview": true,
|
|
166
|
+
"migrationRequired": true,
|
|
167
|
+
"backupBeforeUpgrade": true,
|
|
168
|
+
"healthCheck": {
|
|
169
|
+
"path": "/status",
|
|
170
|
+
"port": 3000,
|
|
171
|
+
"expectedStatus": 200
|
|
172
|
+
}
|
|
173
|
+
}
|
|
@@ -0,0 +1,173 @@
|
|
|
1
|
+
{
|
|
2
|
+
"image": "code.foss.global/serve.zone/cloudly@sha256:9a803fbc9db00ffcf6ce4bd584c0c8b5a3016f3a94ce75629ddee2f52d2bf72c",
|
|
3
|
+
"targetPorts": [
|
|
4
|
+
{
|
|
5
|
+
"name": "web",
|
|
6
|
+
"port": 3000,
|
|
7
|
+
"protocol": "http",
|
|
8
|
+
"default": true
|
|
9
|
+
}
|
|
10
|
+
],
|
|
11
|
+
"envVars": [
|
|
12
|
+
{
|
|
13
|
+
"key": "SERVEZONE_ENVIRONMENT",
|
|
14
|
+
"value": "production",
|
|
15
|
+
"description": "Cloudly runtime environment.",
|
|
16
|
+
"required": true
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"key": "SERVEZONE_PUBLIC_ORIGIN",
|
|
20
|
+
"value": "https://${SERVICE_DOMAIN}",
|
|
21
|
+
"description": "Canonical public Cloudly origin including protocol and optional public port.",
|
|
22
|
+
"required": true
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"key": "SERVEZONE_LISTENPORT",
|
|
26
|
+
"value": "3000",
|
|
27
|
+
"description": "Internal Cloudly HTTP port inside the container.",
|
|
28
|
+
"required": true
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"key": "SERVEZONE_SSLMODE",
|
|
32
|
+
"value": "external",
|
|
33
|
+
"description": "Use external TLS termination through Onebox or dcrouter.",
|
|
34
|
+
"required": true
|
|
35
|
+
},
|
|
36
|
+
{
|
|
37
|
+
"key": "SERVEZONE_SECRET_KEYRING_PATH",
|
|
38
|
+
"value": "/run/secrets/cloudly-secrets-v2-keyring.json",
|
|
39
|
+
"description": "Path to the Cloudly Secrets v2 keyring mounted by Onebox; the keyring value is never placed in the public environment.",
|
|
40
|
+
"required": true
|
|
41
|
+
},
|
|
42
|
+
{
|
|
43
|
+
"key": "SERVEZONE_SECRET_KEYRING_FILE",
|
|
44
|
+
"description": "Existing Cloudly Secrets v2 keyring. Onebox stores it encrypted and mounts it only as a root-readable file; retain the existing keyring when upgrading.",
|
|
45
|
+
"required": true,
|
|
46
|
+
"secret": true,
|
|
47
|
+
"delivery": {
|
|
48
|
+
"type": "file",
|
|
49
|
+
"targetPath": "/run/secrets/cloudly-secrets-v2-keyring.json",
|
|
50
|
+
"uid": 0,
|
|
51
|
+
"gid": 0,
|
|
52
|
+
"mode": 256
|
|
53
|
+
}
|
|
54
|
+
},
|
|
55
|
+
{
|
|
56
|
+
"key": "SERVEZONE_WORKLOADINIT_APPROVAL_PATH",
|
|
57
|
+
"value": "/run/secrets/cloudly-workloadinit-approval.json",
|
|
58
|
+
"description": "Private WorkloadInit release-approval artifact mounted by Onebox for Coreflow secret-runtime registration.",
|
|
59
|
+
"required": true
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"key": "SERVEZONE_WORKLOADINIT_APPROVAL_FILE",
|
|
63
|
+
"description": "Operator-approved WorkloadInit release authority. Onebox stores it encrypted and mounts it only as a root-readable file.",
|
|
64
|
+
"required": true,
|
|
65
|
+
"secret": true,
|
|
66
|
+
"delivery": {
|
|
67
|
+
"type": "file",
|
|
68
|
+
"targetPath": "/run/secrets/cloudly-workloadinit-approval.json",
|
|
69
|
+
"uid": 0,
|
|
70
|
+
"gid": 0,
|
|
71
|
+
"mode": 256
|
|
72
|
+
}
|
|
73
|
+
},
|
|
74
|
+
{
|
|
75
|
+
"key": "MONGODB_URL",
|
|
76
|
+
"value": "${MONGODB_URI}",
|
|
77
|
+
"description": "Authenticated MongoDB wire-protocol URL provisioned by Onebox Corestore.",
|
|
78
|
+
"required": true
|
|
79
|
+
},
|
|
80
|
+
{
|
|
81
|
+
"key": "MONGODB_NAME",
|
|
82
|
+
"value": "${MONGODB_DATABASE}",
|
|
83
|
+
"description": "MongoDB wire-protocol database name provisioned by Onebox Corestore.",
|
|
84
|
+
"required": true
|
|
85
|
+
},
|
|
86
|
+
{
|
|
87
|
+
"key": "MONGODB_USER",
|
|
88
|
+
"value": "${MONGODB_USERNAME}",
|
|
89
|
+
"description": "MongoDB wire-protocol username provisioned by Onebox Corestore.",
|
|
90
|
+
"required": true
|
|
91
|
+
},
|
|
92
|
+
{
|
|
93
|
+
"key": "MONGODB_PASS",
|
|
94
|
+
"value": "${MONGODB_PASSWORD}",
|
|
95
|
+
"description": "MongoDB wire-protocol password provisioned by Onebox Corestore.",
|
|
96
|
+
"required": true
|
|
97
|
+
},
|
|
98
|
+
{
|
|
99
|
+
"key": "S3_ENDPOINT",
|
|
100
|
+
"value": "onebox-corestore",
|
|
101
|
+
"description": "S3 endpoint host provisioned by Onebox Corestore.",
|
|
102
|
+
"required": true
|
|
103
|
+
},
|
|
104
|
+
{
|
|
105
|
+
"key": "S3_PORT",
|
|
106
|
+
"value": "9000",
|
|
107
|
+
"description": "S3 endpoint port provisioned by Onebox Corestore.",
|
|
108
|
+
"required": true
|
|
109
|
+
},
|
|
110
|
+
{
|
|
111
|
+
"key": "S3_USESSL",
|
|
112
|
+
"value": "false",
|
|
113
|
+
"description": "Use plain HTTP for internal Corestore S3 traffic on the Onebox network.",
|
|
114
|
+
"required": true
|
|
115
|
+
},
|
|
116
|
+
{
|
|
117
|
+
"key": "S3_BUCKET",
|
|
118
|
+
"value": "${S3_BUCKET}",
|
|
119
|
+
"description": "S3 bucket provisioned by Onebox Corestore for Cloudly's registry.",
|
|
120
|
+
"required": true
|
|
121
|
+
},
|
|
122
|
+
{
|
|
123
|
+
"key": "S3_ACCESSKEY",
|
|
124
|
+
"value": "${S3_ACCESS_KEY}",
|
|
125
|
+
"description": "S3 access key provisioned by Onebox Corestore.",
|
|
126
|
+
"required": true
|
|
127
|
+
},
|
|
128
|
+
{
|
|
129
|
+
"key": "S3_SECRETKEY",
|
|
130
|
+
"value": "${S3_SECRET_KEY}",
|
|
131
|
+
"description": "S3 secret key provisioned by Onebox Corestore.",
|
|
132
|
+
"required": true
|
|
133
|
+
}
|
|
134
|
+
],
|
|
135
|
+
"platformRequirements": {
|
|
136
|
+
"mongodb": true,
|
|
137
|
+
"s3": true
|
|
138
|
+
},
|
|
139
|
+
"platformOidc": {
|
|
140
|
+
"redirectPath": "/auth/oidc/callback",
|
|
141
|
+
"roles": [
|
|
142
|
+
{
|
|
143
|
+
"id": "admin",
|
|
144
|
+
"label": "Administrator",
|
|
145
|
+
"description": "Full Cloudly administration for this hosted instance."
|
|
146
|
+
},
|
|
147
|
+
{
|
|
148
|
+
"id": "user",
|
|
149
|
+
"label": "User",
|
|
150
|
+
"description": "Standard authenticated Cloudly access for this hosted instance."
|
|
151
|
+
}
|
|
152
|
+
],
|
|
153
|
+
"environmentVariables": {
|
|
154
|
+
"issuerUrl": "SERVEZONE_PLATFORM_OIDC_ISSUER",
|
|
155
|
+
"clientId": "SERVEZONE_PLATFORM_OIDC_CLIENT_ID",
|
|
156
|
+
"clientSecret": "SERVEZONE_PLATFORM_OIDC_CLIENT_SECRET",
|
|
157
|
+
"redirectUri": "SERVEZONE_PLATFORM_OIDC_REDIRECT_URI",
|
|
158
|
+
"audience": "SERVEZONE_PLATFORM_OIDC_AUDIENCE"
|
|
159
|
+
},
|
|
160
|
+
"clientAuthenticationMethod": "client_secret_basic"
|
|
161
|
+
},
|
|
162
|
+
"minOneboxVersion": "32.4.0",
|
|
163
|
+
"changelog": "Move Cloudly to 33.5.0, a feature release over 33.4.0: a deployment is reserved only by a deployment machine user. reserveServiceDeployment refuses any other verified actor, an administrator included, with DEPLOYMENT_MACHINE_IDENTITY_REQUIRED before anything is reserved, and the reserve-phase getDeploymentPreflight reports the same blocker; an existing api machine user with its grants already qualifies and needs no change. A deployer that signs in with a username and password, such as tsdeploy with TSDEPLOY_CLOUDLY_USERNAME and TSDEPLOY_CLOUDLY_PASSWORD, is an administrator and is refused, so switch it to a machine-user token before upgrading: create a deployment machine user per deployer with mutateDeploymentMachineUser or Access → Deployment machine users in the dashboard, attach its grants with configureServiceDeploymentMachineUser, and give its username and token to the deployer. An operation an administrator reserved earlier stays awaiting its image; clean it up with cleanupServiceDeployment. mutateDeploymentMachineUser creates an API machine user with one token (create), replaces every token of one with a new token (rotate-token) or removes its tokens while its grants stay (revoke-token); the token is answered once and expires at most a year after the mutation, and getDeploymentMachineUsers lists every deployment machine user with its token expiries and grants and never a token value. The identity getIdentityByToken issues and the registry bearer of a machine login now name the SHA-256 of their token, and every verification checks that the user still holds that unexpired token, so removing a token ends the sessions opened with it. A machine identity or registry bearer issued by an earlier release names no token and is refused, so its holder exchanges its token again: a deployer such as tsdeploy does so on every run, while a long-running API or administrator machine client that keeps its identity across a reconnect calls getIdentityByToken once more after the upgrade; cluster identities, including relays on the shared cluster token, and service workload identities are unaffected. Let no deployment run while Cloudly upgrades: a run in progress keeps its pre-upgrade identity and is refused for the rest of that run, so rerun it or resume it with deploy-retry. The cluster config broadcast now reaches the elected relay of every cluster, so a Corestore endpoint written on a node of a Pallet cluster, and every other broadcast, reaches that cluster's relay at once instead of when it reconnects, and setServiceRuntimeSpec refuses a spec the runtime spec contract rejects as Service runtime operation rejected: invalid. instead of Internal server error, and stores nothing. The runtime contract is unchanged from 1.7.0 and requires Onebox 32.4.0. Cloudly 33.5.0 stores the retained mutation answers in the new collection cloudly_deployment_machine_user_mutations and keeps the data version 0.22.0, so from 1.7.0 there is no data step. From 1.6.0, startup runs the forward-only data migration from 0.21.0 to 0.22.0 through the step runtime-session-protocol-offer, which states protocol: null on every Pallet session row recorded before Cloudly stored the protocol offer its node stated, so such a node counts as unrecorded until it registers again; stop Cloudly and take a verified backup before upgrading, because the step has no inverse and rollback requires a full restore. The published-port ranges of Cloudly 33.4.0 apply too: setServicePublishedPorts publishes a contiguous range through hostPortEnd and same-port outbound through symmetric: true, which needs public egress (published-port-symmetric-without-egress) and owns its inside ports (published-port-symmetric-inside-overlap); new handoff leases translate outbound flows only into the SNAT band 49152-65535, whose ports are refused published-port-reserved, while a node keeps its 1024-65535 lease until its router is re-created; a service network policy write for a service whose deletion has begun is refused service-deleting; and a projection carrying a range or a symmetric entry is withheld as node-contract-behind from a Pallet node whose session states a release below interfaces 32.31.0, or none. From 1.5.0 the same step runs, and the service network egress of Cloudly 33.3.0 applies too: an administrator sets a service's network egress with setServiceNetworkEgress, which states whether the service's attached workloads reach the public internet and which platform endpoints of the protected authority they reach, and reads it with getServiceNetworkEgress; a workload whose enabled database or object-storage binding sits on a node whose Corestore endpoint its network does not select is refused database-endpoint-unselected or objectstorage-endpoint-unselected, and a replica already running keeps running while its target reports the refusal, so grant the endpoint through the service's egress before such a workload is placed again; the default runtime spec of a new service probes its process instead of its first TCP target port. From 1.4.0 the same step runs, and the gateway admin bootstrap of Cloudly 33.2.0 applies too: an administrator hands Cloudly a dcrouter admin token once through bootstrapExternalGatewayCredential or servezone gateway bootstrap, from which Cloudly provisions and stores its own gateway-client credential; a first enrollment turns admin-bootstrap-required, a gateway settings change the held credential cannot carry is staged, a runtime network address plan out of its canonical order is refused plan-unsorted, and a relay naming a node Cloudly does not hold is refused relay-node-unknown: roll out Cloudly 33.5.0 first, then Coreflow 33.2.0, which recognises the relay-node-unknown refusal. From 1.3.0 the same step runs, and the per-node database endpoint of Cloudly 33.1.0 applies too: roll out Cloudly 33.5.0 first, then Coreflow 33.2.0 (33.1.0 at minimum), then Corestore 33.0.0, and set every node's Corestore database endpoint with setClusterNodeCorestoreDatabaseEndpoint, because a database binding on a node without one is not granted and its service is refused database-endpoint-missing, and existing database bindings answer no credential material until they are granted again for the endpoint. From 1.2.1 or earlier, startup runs the forward-only data migration from 0.20.0 to 0.21.0 through the step retire-cluster-relay-acme and then the step runtime-session-protocol-offer to 0.22.0; retire-cluster-relay-acme drops the relay certificate and DNS collections of Cloudly's retired Cloudflare and Let's Encrypt integration and logs every relay name whose A record Cloudly had written at Cloudflare: remove each such record at the provider. A cluster relay then requires a dcrouter that advertises dns.clientRecords and certificates.exactIssuance, SERVEZONE_SSLMODE=letsencrypt is refused (this template keeps external), and the typed API changes as the Breaking Changes of the Cloudly 33.0.0 changelog list; review them, stop Cloudly and take a verified backup before upgrading, because the 32.9 image refuses the migrated data and rollback requires a full restore. The upgrade is marked breaking and manual-review because a username and password deployer, an administrator's deployment reservation and a machine identity or registry bearer issued earlier are refused, and migration-required and backup-before-upgrade because these flags are read from the target version alone, every upgrade from 1.6.0 or earlier runs the 0.21.0 to 0.22.0 step, and an upgrade from 1.2.1 or earlier still runs the migration from 0.20.0 on this image as well. An installation on 1.1.10 or earlier also runs the 1.2.0 steps first, from 0.10.0, and requires completed Secrets v2 cutover retirement. Preserve existing user and storage identities, OIDC bindings, the encrypted keyring and WorkloadInit approval as dedicated root-readable files.",
|
|
164
|
+
"breaking": true,
|
|
165
|
+
"requiresManualReview": true,
|
|
166
|
+
"migrationRequired": true,
|
|
167
|
+
"backupBeforeUpgrade": true,
|
|
168
|
+
"healthCheck": {
|
|
169
|
+
"path": "/status",
|
|
170
|
+
"port": 3000,
|
|
171
|
+
"expectedStatus": 200
|
|
172
|
+
}
|
|
173
|
+
}
|
package/appstore.json
CHANGED
|
@@ -151,7 +151,7 @@
|
|
|
151
151
|
"description": "Multi-node serve.zone control plane for clusters, workload services, domains, and deployments.",
|
|
152
152
|
"category": "Dev Tools",
|
|
153
153
|
"iconName": "server",
|
|
154
|
-
"latestVersion": "1.
|
|
154
|
+
"latestVersion": "1.8.0",
|
|
155
155
|
"tags": ["serve.zone", "control-plane", "clusters", "deployments"]
|
|
156
156
|
},
|
|
157
157
|
{
|
package/changelog.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 2026-09-28 - 32.8.0
|
|
4
|
+
|
|
5
|
+
### Features
|
|
6
|
+
|
|
7
|
+
- publish the Cloudly 1.8.0 template for Cloudly 33.5.0 (cloudly)
|
|
8
|
+
- Add Cloudly app version 1.8.0, pinned to the Cloudly 33.5.0 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:9a803fbc9db00ffcf6ce4bd584c0c8b5a3016f3a94ce75629ddee2f52d2bf72c` (linux/amd64 and linux/arm64), and mark it as the latest catalog version.
|
|
9
|
+
- Keep the 1.7.0 runtime contract and `minOneboxVersion` 32.4.0. Cloudly 33.5.0 changes neither `qenv.yml` nor the Dockerfile and reads no new environment variable, so every start-required variable is still a required template variable and `SERVEZONE_SSLMODE` stays `external`.
|
|
10
|
+
- Mark the upgrade breaking and manual-review, because Cloudly 33.5.0 reserves a deployment only for a deployment machine user (`DEPLOYMENT_MACHINE_IDENTITY_REQUIRED` refuses an administrator and a username and password deployer such as tsdeploy with `TSDEPLOY_CLOUDLY_USERNAME`/`TSDEPLOY_CLOUDLY_PASSWORD`, which switches to a machine-user token before the upgrade), refuses a machine identity or registry bearer issued by an earlier release until its holder exchanges its token again, and refuses for the rest of its run a deployment in progress during the upgrade. Keep it migration-required and backup-before-upgrade: 33.5.0 adds the collection `cloudly_deployment_machine_user_mutations` without a data step and keeps data version 0.22.0, so from 1.7.0 there is no data step, but hosts read these flags from the target version alone and an installation on 1.6.0 or earlier still runs the forward-only step `runtime-session-protocol-offer` from 0.21.0 to 0.22.0 on this image (and one on 1.2.1 or earlier the 0.20.0 → 0.21.0 migration of Cloudly 33.0.0 before it). The template changelog names `mutateDeploymentMachineUser` (`create`, `rotate-token`, `revoke-token`), `getDeploymentMachineUsers`, the dashboard's Access → Deployment machine users, `configureServiceDeploymentMachineUser`, `cleanupServiceDeployment` for an operation an administrator reserved earlier, the token-bound machine sessions that end when their token is removed, the relay config push to the elected relay of every cluster, and the `invalid` refusal of `setServiceRuntimeSpec`. For installations on 1.6.0 it carries forward the published-port ranges of Cloudly 33.4.0, and for 1.5.0, 1.4.0, 1.3.0 and earlier the service network egress of Cloudly 33.3.0, the gateway admin bootstrap of Cloudly 33.2.0 with the rollout order Cloudly 33.5.0 before Coreflow 33.2.0, the per-node Corestore database endpoint and the prerequisites of the 33.0.0 migration, as 1.7.0 did.
|
|
11
|
+
- Update the bundled client data, the README guidance and the resolver regression coverage, which now holds 1.8.0 to the 1.7.0 runtime contract and upgrade flags.
|
|
12
|
+
|
|
13
|
+
## 2026-09-28 - 32.7.0
|
|
14
|
+
|
|
15
|
+
### Features
|
|
16
|
+
|
|
17
|
+
- publish the Cloudly 1.7.0 template for Cloudly 33.4.0 (cloudly)
|
|
18
|
+
- Add Cloudly app version 1.7.0, pinned to the Cloudly 33.4.0 multi-platform image index `code.foss.global/serve.zone/cloudly@sha256:f4f88f0c3765d1b129fa4f3ff68438958e55d4fad598393fb0c686261e46c7ed` (linux/amd64 and linux/arm64), and mark it as the latest catalog version.
|
|
19
|
+
- Keep the 1.6.0 runtime contract and `minOneboxVersion` 32.4.0. Cloudly 33.4.0 changes neither `qenv.yml` nor the Dockerfile and reads no new environment variable, so every start-required variable is still a required template variable and `SERVEZONE_SSLMODE` stays `external`.
|
|
20
|
+
- Mark the upgrade breaking, migration-required, backup-before-upgrade and manual-review. Hosts read these flags from the target version alone, and every installation on 1.6.0 or earlier now runs the forward-only data step `runtime-session-protocol-offer` from 0.21.0 to 0.22.0, which states `protocol: null` on earlier Pallet session rows (backup first, full-restore rollback); an installation on 1.2.1 or earlier runs the 0.20.0 → 0.21.0 migration of Cloudly 33.0.0 before it. The template changelog names published-port ranges (`hostPortEnd`, at most 1024 ports per protocol) and symmetric same-port outbound (`symmetric: true`, which needs public egress), the 49152-65535 SNAT band of new handoff leases (an existing lease keeps 1024-65535 until its router is re-created), the refusals `published-port-reserved`, `published-port-symmetric-without-egress`, `published-port-symmetric-inside-overlap` and `service-deleting`, and the `node-contract-behind` withholding of a projection with ranges or symmetric entries from a Pallet node whose session states a release below interfaces 32.31.0, or an unrecorded one, so ranges and symmetric entries take effect on a node only once it runs a Pallet release built on interfaces 32.31.0 or later. For installations on 1.5.0, 1.4.0, 1.3.0 and earlier it carries forward the service network egress of Cloudly 33.3.0, the gateway admin bootstrap of Cloudly 33.2.0 with the rollout order Cloudly 33.4.0 before Coreflow 33.2.0, the per-node Corestore database endpoint and the prerequisites of the 33.0.0 migration, as 1.6.0 did.
|
|
21
|
+
- Update the bundled client data, the README guidance and the resolver regression coverage, which now holds 1.7.0 to the 1.6.0 runtime contract and upgrade flags.
|
|
22
|
+
|
|
3
23
|
## 2026-09-27 - 32.6.0
|
|
4
24
|
|
|
5
25
|
### Features
|