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
Copy file name to clipboardExpand all lines: docs/home/release-notes.md
-276Lines changed: 0 additions & 276 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -245,279 +245,3 @@ Things that you have keep in mind before upgrading process:
245
245
repository: busybox
246
246
tag: 1.36.1
247
247
```
248
-
249
-
## Version 1.57
250
-
251
-
!!! danger
252
-
253
-
This version must be installed before proceeding with the next update.
254
-
255
-
!!! tip ""
256
-
Helm chart version 1.57.0
257
-
258
-
### Helm configuration changes
259
-
260
-
- Removed the link to the database for the service `func-file`. If you have it in your `values.yaml`, then you can safely remove the `spring` map completely.
261
-
262
-
```yaml
263
-
funcFile:
264
-
configurationFiles:
265
-
"application.yaml":
266
-
spring:
267
-
datasource:
268
-
# -- Mysql jdbc URL
269
-
url: "jdbc:mysql://..."
270
-
```
271
-
272
-
- For the Clickhouse `busybox` image, the ability to set the repository and version has been added.
273
-
274
-
```yaml
275
-
clickhouse:
276
-
busyboxImage:
277
-
# -- Image registry
278
-
registry: docker.io
279
-
# -- Image repository
280
-
repository: busybox
281
-
# -- Image tag
282
-
tag: 1.36.1
283
-
```
284
-
285
-
## Version 1.56
286
-
287
-
!!! tip ""
288
-
Helm chart version 1.56.1
289
-
290
-
### Export metrics to Genestack
291
-
292
-
Fluent-bit was introduced as an extra service tasked with collecting and dispatching metrics in Prometheus format to a Genestack.
293
-
294
-
These metrics encompass technical and/or product-related data, devoid of any sensitive information.
295
-
296
-
If you wish to deactivate this functionality, you can do so by configuring the following parameter:
297
-
298
-
```yaml
299
-
fluent-bit:
300
-
enabled: false
301
-
```
302
-
303
-
### Helm configuration changes
304
-
305
-
Now organization name and hostname are in a `global` section:
306
-
307
-
From:
308
-
309
-
```yaml
310
-
odmFrontendHostname: odm.local
311
-
applications:
312
-
configurationFiles:
313
-
"application.yaml":
314
-
frontend:
315
-
ui:
316
-
organization:
317
-
name: "Genestack"
318
-
```
319
-
320
-
To:
321
-
322
-
```yaml
323
-
global:
324
-
hostname: odm.local
325
-
organizationName: "Genestack"
326
-
```
327
-
328
-
## Version 1.55
329
-
330
-
!!! tip ""
331
-
Helm chart version 1.55.4
332
-
333
-
### Configure ODM usage together with encrypted S3 bucket (SSE-KMS and SSE-S3 only)
334
-
335
-
#### Introduction
336
-
337
-
!!! attention ""
338
-
You can find configuration examples in the ODM Helm chart.
339
-
340
-
In case you have several AWS credentials in your configuration, you need to modify only the credentials for
341
-
accessing the bucket in specified as `frontend.aws.bucket`.
342
-
343
-
#### SSE-KMS
344
-
345
-
To enable uploading into an SSE-KMS encrypted bucket, you need to customize `func-file` configuration.
346
-
The following configuration example uses a bucket encrypted by SSE-KMS with the name `<BUCKET_NAME>`.
347
-
The bucket configuration should specify the algorithm `aws:kms` as `preferredAlgorithm`. Additionally,
348
-
the property `kmsCmkId` should be added with a value equal to key id `arn:aws:kms:...` if the bucket policy
349
-
requires this key to be explicitly send on PUT request. The `func-file` section in the configuration
350
-
should look like this:
351
-
352
-
#### SSE-S3
353
-
354
-
The SSE-S3 encryption type is default to the most buckets. To force ODM request
355
-
this type of encryption from S3 provider for `<BUCKET_NAME>`, you need to specify
356
-
the `preferredAlgorithm` property with the value `AES256`:
357
-
358
-
#### On `storage_config` section configuration in `func-file`
359
-
360
-
Keep in mind that `func-file` reads the `storage_config` section sequentially. You can create specific configurations
361
-
for individual buckets, e.g., if one has SSE-KMS encryption while others do not. To do this, as the first item in
362
-
the list, you'll need to specify the bucket with the specific configuration and its name. Then, provide the general
363
-
configuration for the other buckets using the wildcard symbol `*`. ODM will only upload files to the bucket, specified
364
-
as `frontend.aws.bucket` property, regardless to `storage_config` section.
365
-
366
-
### Genestack pod separation
367
-
368
-
Example on the image section, but it's applicable for sections with backend/frontend separation.
0 commit comments