Skip to content

Commit 554eeda

Browse files
metal-robot[bot]metal-stack
andauthored
Bump releases to version v0.22.9 (#257)
* Bump releases to version v0.22.9 * Auto generate --------- Co-authored-by: metal-stack <info@metal-stack.io>
1 parent 5583247 commit 554eeda

5 files changed

Lines changed: 223 additions & 1 deletion

File tree

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
slug: /release-notes/v0.22.9
3+
title: v0.22.9
4+
sidebar_position: 1
5+
---
6+
# metal-stack v0.22.9
7+
See original release note at [https://github.com/metal-stack/releases/releases/tag/v0.22.9](https://github.com/metal-stack/releases/releases/tag/v0.22.9)
8+
## General
9+
* [Gardener v1.128](https://github.com/gardener/gardener/releases/tag/v1.128.0)
10+
* Please note that this release contains the gardener-apiserver built from the metal-stack fork in order to prevent the defaulting of worker machine images by Gardener. This will be resolved upstream with https://github.com/gardener/gardener/pull/13785. If you do not use short image versions in the `CloudProfile` you can also use the upstream version of the gardener-apiserver.
11+
## Required Actions
12+
* Update existing zitadel-init configurations in your deployment (`zitadel_init_config`) to use `redirect_uris` instead of `redirect_uri`. (metal-stack/zitadel-init#9)
13+
* If during reconciles of old shoots the following shoot error occurs: `ScrapeConfig.monitoring.coreos.com "shoot-blackbox-exporter-k8s-service-check is invalid: spec.kubernetesSDConfigs[0].role: Unsupported value: "service"`, it is enough to edit the `ScrapeConfig` in the shoot namespace in the `Seed` and correct `service` to `Service`.
14+
## Component Releases
15+
### metal-roles v0.20.1
16+
* Use new OCI helm-charts from metal-stack. (metal-stack/metal-roles#582) @Gerrit91
17+
* Add param for deploying `ClusterRoleBinding`s into the virtual garden. (metal-stack/metal-roles#585) @Gerrit91
18+
### api v0.0.61
19+
* Machine create refinements (metal-stack/api#119) @majst01
20+
* Map validations (metal-stack/api#122) @majst01
21+
### node-init v0.1.8
22+
* Update actions workflows and dependencies. (metal-stack/node-init#20) @Gerrit91
23+
* feat: configure HTTP transport for persistent connections to kube-apiserver (metal-stack/node-init#19) @mwennrich
24+
* include sbom in container image (metal-stack/node-init#17) @mac641
25+
### zitadel-init v0.3.3
26+
* Allow configuration of multiple redirect URIs. (metal-stack/zitadel-init#9) @Gerrit91
27+
# Merged Pull Requests
28+
This is a list of pull requests that were merged since the last release. The list does not contain pull requests from release-vector-repositories.
29+
30+
The fact that these pull requests were merged does not necessarily imply that they have already become part of this metal-stack release.
31+
32+
* More documentation for release-drafter action. (metal-stack/actions-common#6) @Gerrit91
33+
* Provide common helm-chart action. (metal-stack/actions-common#7) @Gerrit91
34+
* chore: blog maintainers (metal-stack/website#253) @vknabel
35+
* Bump releases to version v0.22.8 (metal-stack/website#252) @metal-robot[bot]
36+
* Remove unnecessary braces from if conditions. (metal-stack/actions-common#9) @Gerrit91
37+
* Fix issue comments only working on pull requests. (metal-stack/metal-robot#108) @Gerrit91
38+
* chore(deps): bump postcss from 8.5.9 to 8.5.10 in the other-dependencies group (metal-stack/website#251) @dependabot[bot]
39+
* chore(deps): bump the docusaurus-dependencies group with 2 updates (metal-stack/website#250) @dependabot[bot]
40+
* Allow repo maintainers to run comment actions. (metal-stack/metal-robot#109) @Gerrit91
41+
* Support more chassistypes (metal-stack/go-hal#86) @majst01
42+
* Improved test coverage (metal-stack/cli#29) @AnnaSchreiner
43+
* Enter serial console (metal-stack/go-hal#87) @majst01
44+
* Remove security.User from auditing and split http/grpc/connect (metal-stack/metal-lib#206) @majst01
45+
* chore(ci): actions-common (metal-stack/metal-robot#110) @vknabel
46+
* chore(deps): bump the docusaurus-dependencies group with 2 updates (metal-stack/website#254) @dependabot[bot]
47+
* chore(deps): bump the other-dependencies group across 1 directory with 5 updates (metal-stack/website#255) @dependabot[bot]
48+
* Migrate to web-only UI (metal-stack/metal-ui#11) @ostempel
49+
* Dependency updates. (metal-stack/cli#30) @Gerrit91
50+
* adjust metal-ui skill and remove tauri leftovers (metal-stack/metal-ui#12) @ostempel
51+
* Add rule template. (metal-stack/website#256) @Gerrit91
52+
* Next release (metal-stack/releases#284) @metal-robot[bot]

docs/08-References/Storage/csi-driver-lvm/csi-driver-lvm.md

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,9 +49,68 @@ Now you can use one of following storageClasses:
4949
* `csi-driver-lvm-linear`
5050
* `csi-driver-lvm-mirror`
5151
* `csi-driver-lvm-striped`
52+
* `csi-driver-lvm-linear-encrypted`
53+
* `csi-driver-lvm-mirror-encrypted`
54+
* `csi-driver-lvm-striped-encrypted`
5255

5356
To get the previous old and now deprecated `csi-lvm-sc-linear`, ... storageclasses, set helm-chart value `compat03x=true`.
5457

58+
## Encryption ##
59+
60+
csi-driver-lvm supports LUKS2 encryption for volumes at rest. When encryption is enabled, the LVM logical volume is formatted with LUKS2 and a dm-crypt mapper device is used transparently for all I/O.
61+
62+
### Setup ###
63+
64+
1. Create a Kubernetes Secret containing the LUKS passphrase:
65+
66+
```bash
67+
kubectl create secret generic csi-lvm-encryption-secret \
68+
--from-literal=passphrase='my-secret-passphrase'
69+
```
70+
71+
2. Enable the encrypted StorageClasses in your Helm values (they are disabled by default):
72+
73+
```yaml
74+
storageClasses:
75+
linearEncrypted:
76+
enabled: true
77+
mirrorEncrypted:
78+
enabled: true
79+
stripedEncrypted:
80+
enabled: true
81+
```
82+
83+
3. Create PVCs using one of the encrypted StorageClasses. The encryption is handled transparently by the driver.
84+
85+
### How it works ###
86+
87+
- **NodeStageVolume**: LUKS-formats the LV (first use only), then opens it via `cryptsetup luksOpen`, creating a `/dev/mapper/csi-lvm-<volumeID>` device
88+
- **NodePublishVolume**: Mounts the mapper device (instead of the raw LV) to the target path
89+
- **NodeUnpublishVolume**: Unmounts as usual
90+
- **NodeUnstageVolume**: Closes the LUKS device via `cryptsetup luksClose`
91+
- **Volume expansion**: The LV is extended first, then the LUKS layer is resized, then the filesystem
92+
93+
Both filesystem and raw block access types are supported with encryption.
94+
95+
### Encrypted Ephemeral Volumes ###
96+
97+
Encryption is also supported for CSI ephemeral (inline) volumes. Since ephemeral volumes bypass `NodeStageVolume`, the LUKS formatting and opening is handled directly during `NodePublishVolume`, and the LUKS device is closed during `NodeUnpublishVolume`.
98+
99+
To use an encrypted ephemeral volume, specify `encryption: "true"` in `volumeAttributes` and reference the encryption secret via `nodePublishSecretRef`:
100+
101+
```yaml
102+
volumes:
103+
- name: encrypted-ephemeral
104+
csi:
105+
driver: lvm.csi.metal-stack.io
106+
volumeAttributes:
107+
size: "100Mi"
108+
type: "linear"
109+
encryption: "true"
110+
nodePublishSecretRef:
111+
name: csi-lvm-encryption-secret
112+
```
113+
55114
## Migration ##
56115

57116
If you want to migrate your existing PVC to / from csi-driver-lvm, you can use [korb](https://github.com/BeryJu/korb).

src/version.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
{"version": "v0.22.8"}
1+
{"version": "v0.22.9"}
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
slug: /release-notes/v0.22.9
3+
title: v0.22.9
4+
sidebar_position: 1
5+
---
6+
# metal-stack v0.22.9
7+
See original release note at [https://github.com/metal-stack/releases/releases/tag/v0.22.9](https://github.com/metal-stack/releases/releases/tag/v0.22.9)
8+
## General
9+
* [Gardener v1.128](https://github.com/gardener/gardener/releases/tag/v1.128.0)
10+
* Please note that this release contains the gardener-apiserver built from the metal-stack fork in order to prevent the defaulting of worker machine images by Gardener. This will be resolved upstream with https://github.com/gardener/gardener/pull/13785. If you do not use short image versions in the `CloudProfile` you can also use the upstream version of the gardener-apiserver.
11+
## Required Actions
12+
* Update existing zitadel-init configurations in your deployment (`zitadel_init_config`) to use `redirect_uris` instead of `redirect_uri`. (metal-stack/zitadel-init#9)
13+
* If during reconciles of old shoots the following shoot error occurs: `ScrapeConfig.monitoring.coreos.com "shoot-blackbox-exporter-k8s-service-check is invalid: spec.kubernetesSDConfigs[0].role: Unsupported value: "service"`, it is enough to edit the `ScrapeConfig` in the shoot namespace in the `Seed` and correct `service` to `Service`.
14+
## Component Releases
15+
### metal-roles v0.20.1
16+
* Use new OCI helm-charts from metal-stack. (metal-stack/metal-roles#582) @Gerrit91
17+
* Add param for deploying `ClusterRoleBinding`s into the virtual garden. (metal-stack/metal-roles#585) @Gerrit91
18+
### api v0.0.61
19+
* Machine create refinements (metal-stack/api#119) @majst01
20+
* Map validations (metal-stack/api#122) @majst01
21+
### node-init v0.1.8
22+
* Update actions workflows and dependencies. (metal-stack/node-init#20) @Gerrit91
23+
* feat: configure HTTP transport for persistent connections to kube-apiserver (metal-stack/node-init#19) @mwennrich
24+
* include sbom in container image (metal-stack/node-init#17) @mac641
25+
### zitadel-init v0.3.3
26+
* Allow configuration of multiple redirect URIs. (metal-stack/zitadel-init#9) @Gerrit91
27+
# Merged Pull Requests
28+
This is a list of pull requests that were merged since the last release. The list does not contain pull requests from release-vector-repositories.
29+
30+
The fact that these pull requests were merged does not necessarily imply that they have already become part of this metal-stack release.
31+
32+
* More documentation for release-drafter action. (metal-stack/actions-common#6) @Gerrit91
33+
* Provide common helm-chart action. (metal-stack/actions-common#7) @Gerrit91
34+
* chore: blog maintainers (metal-stack/website#253) @vknabel
35+
* Bump releases to version v0.22.8 (metal-stack/website#252) @metal-robot[bot]
36+
* Remove unnecessary braces from if conditions. (metal-stack/actions-common#9) @Gerrit91
37+
* Fix issue comments only working on pull requests. (metal-stack/metal-robot#108) @Gerrit91
38+
* chore(deps): bump postcss from 8.5.9 to 8.5.10 in the other-dependencies group (metal-stack/website#251) @dependabot[bot]
39+
* chore(deps): bump the docusaurus-dependencies group with 2 updates (metal-stack/website#250) @dependabot[bot]
40+
* Allow repo maintainers to run comment actions. (metal-stack/metal-robot#109) @Gerrit91
41+
* Support more chassistypes (metal-stack/go-hal#86) @majst01
42+
* Improved test coverage (metal-stack/cli#29) @AnnaSchreiner
43+
* Enter serial console (metal-stack/go-hal#87) @majst01
44+
* Remove security.User from auditing and split http/grpc/connect (metal-stack/metal-lib#206) @majst01
45+
* chore(ci): actions-common (metal-stack/metal-robot#110) @vknabel
46+
* chore(deps): bump the docusaurus-dependencies group with 2 updates (metal-stack/website#254) @dependabot[bot]
47+
* chore(deps): bump the other-dependencies group across 1 directory with 5 updates (metal-stack/website#255) @dependabot[bot]
48+
* Migrate to web-only UI (metal-stack/metal-ui#11) @ostempel
49+
* Dependency updates. (metal-stack/cli#30) @Gerrit91
50+
* adjust metal-ui skill and remove tauri leftovers (metal-stack/metal-ui#12) @ostempel
51+
* Add rule template. (metal-stack/website#256) @Gerrit91
52+
* Next release (metal-stack/releases#284) @metal-robot[bot]

versioned_docs/version-v0.22/08-References/Storage/csi-driver-lvm/csi-driver-lvm.md

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,9 +49,68 @@ Now you can use one of following storageClasses:
4949
* `csi-driver-lvm-linear`
5050
* `csi-driver-lvm-mirror`
5151
* `csi-driver-lvm-striped`
52+
* `csi-driver-lvm-linear-encrypted`
53+
* `csi-driver-lvm-mirror-encrypted`
54+
* `csi-driver-lvm-striped-encrypted`
5255

5356
To get the previous old and now deprecated `csi-lvm-sc-linear`, ... storageclasses, set helm-chart value `compat03x=true`.
5457

58+
## Encryption ##
59+
60+
csi-driver-lvm supports LUKS2 encryption for volumes at rest. When encryption is enabled, the LVM logical volume is formatted with LUKS2 and a dm-crypt mapper device is used transparently for all I/O.
61+
62+
### Setup ###
63+
64+
1. Create a Kubernetes Secret containing the LUKS passphrase:
65+
66+
```bash
67+
kubectl create secret generic csi-lvm-encryption-secret \
68+
--from-literal=passphrase='my-secret-passphrase'
69+
```
70+
71+
2. Enable the encrypted StorageClasses in your Helm values (they are disabled by default):
72+
73+
```yaml
74+
storageClasses:
75+
linearEncrypted:
76+
enabled: true
77+
mirrorEncrypted:
78+
enabled: true
79+
stripedEncrypted:
80+
enabled: true
81+
```
82+
83+
3. Create PVCs using one of the encrypted StorageClasses. The encryption is handled transparently by the driver.
84+
85+
### How it works ###
86+
87+
- **NodeStageVolume**: LUKS-formats the LV (first use only), then opens it via `cryptsetup luksOpen`, creating a `/dev/mapper/csi-lvm-<volumeID>` device
88+
- **NodePublishVolume**: Mounts the mapper device (instead of the raw LV) to the target path
89+
- **NodeUnpublishVolume**: Unmounts as usual
90+
- **NodeUnstageVolume**: Closes the LUKS device via `cryptsetup luksClose`
91+
- **Volume expansion**: The LV is extended first, then the LUKS layer is resized, then the filesystem
92+
93+
Both filesystem and raw block access types are supported with encryption.
94+
95+
### Encrypted Ephemeral Volumes ###
96+
97+
Encryption is also supported for CSI ephemeral (inline) volumes. Since ephemeral volumes bypass `NodeStageVolume`, the LUKS formatting and opening is handled directly during `NodePublishVolume`, and the LUKS device is closed during `NodeUnpublishVolume`.
98+
99+
To use an encrypted ephemeral volume, specify `encryption: "true"` in `volumeAttributes` and reference the encryption secret via `nodePublishSecretRef`:
100+
101+
```yaml
102+
volumes:
103+
- name: encrypted-ephemeral
104+
csi:
105+
driver: lvm.csi.metal-stack.io
106+
volumeAttributes:
107+
size: "100Mi"
108+
type: "linear"
109+
encryption: "true"
110+
nodePublishSecretRef:
111+
name: csi-lvm-encryption-secret
112+
```
113+
55114
## Migration ##
56115

57116
If you want to migrate your existing PVC to / from csi-driver-lvm, you can use [korb](https://github.com/BeryJu/korb).

0 commit comments

Comments
 (0)