Merge branch 'release/v6.0.1'

Author: Leon

.blueprint-override.yaml.template

@@ -1,3 +1,4 @@
+# copy this to .blueprint-override.yaml to override the default blueprint
 apiVersion: k8s.cloudogu.com/v3
 kind: Blueprint
 metadata:

.ecosystem-core-values-patch.yaml.template

@@ -0,0 +1,5 @@
+# copy this to .ecosystem-core-values-patch.yaml to patch the default values
+backup:
+  enabled: true
+monitoring:
+  enabled: true

.gitignore

@@ -25,7 +25,11 @@ terraform.tfvars
 .additionalValues.yaml
 # generated blueprint file
 .blueprint.yaml
+
+# override and patch files
 .blueprint-override.yaml
+.longhorn-values-patch.yaml
+.ecosystem-core-values-patch.yaml
 
 **/gcp_sa.json
 **/.terraform

.longhorn-values-patch.yaml.template

@@ -0,0 +1,4 @@
+# copy this to longhorn-values-patch.yaml to patch the default values
+defaultBackupStore:
+  backupTarget: s3://longhorn@dummyregion/
+  backupTargetCredentialSecret: longhorn-backup-target

CHANGELOG.md

@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [v6.0.1] - 2026-06-02
+### Changed
+- [#142] activate Cilium NetworkPolicy in terraform module
+
 ## [v6.0.0] - 2026-04-13
 ### Changed
  - [#137] prepare modules for using with ecosystem-core v4

docs/development/.lop-idp-blueprint-override.yaml

@@ -0,0 +1,35 @@
+apiVersion: k8s.cloudogu.com/v3
+kind: Blueprint
+metadata:
+  labels:
+    app: ces
+    app.kubernetes.io/name: k8s-blueprint-lib
+  name: blueprint
+spec:
+  displayName: "k3ces.localdomain"
+  stopped: false
+  blueprint:
+    dogus: []
+    config:
+      dogus: {}
+      global:
+        - key: "fqdn"
+          value: "k3ces.localdomain"
+        - key: "domain"
+          value: "k3ces.localdomain"
+        # should be set to "external" for mk-cert
+        - key: "certificate/type"
+          value: "selfsigned"
+        - key: "password-policy/min_length"
+          value: "1"
+        - key: "password-policy/must_contain_capital_letter"
+          value: "false"
+        - key: "password-policy/must_contain_digit"
+          value: "false"
+        - key: "password-policy/must_contain_lower_case_letter"
+          value: "false"
+        - key: "password-policy/must_contain_special_character"
+          value: "false"
+  blueprintMask:
+    manifest:
+      dogus: []

docs/development/.lop-idp-ecosystem-core-values-patch.yaml

@@ -0,0 +1,27 @@
+components:
+  lop-idp:
+    version: 1.1.0
+    valuesObject:
+      defaultConfig:
+        env:
+          initialDomain: "k3ces.localdomain"
+      ldap:
+        secrets:
+          initialAdminPasswordSecretRef:
+            create: false
+            name: initial-admin-password
+            passwordKey: admin-password
+      cas:
+        configuration:
+          normal:
+            allow_local_urls: "true"
+  k8s-dogu-operator:
+    valuesObject:
+      controllerManager:
+        env:
+          authRegistrationEnabled: true
+          disablePostfixDependencyCheck: true
+  k8s-auth-registration-crd:
+    version: 1.0.0
+  postfix:
+    version: 3.10.8-3

docs/development/dev_box_de.md

@@ -120,6 +120,30 @@ Wenn das der Fall ist, werden keine weiteren Schritte ausgeführt.
 Über die Konfiguration `forceUpgradeEcosystem` in der `.vagrant.rb`-Datei, kann dieses Verhalten deaktiviert werden.
 Dann wird das Helm-Release `ecosystem-core` und das Blueprint bei jedem `vagrant up` aktualisiert.
 
+#### Ecosystem-Core-Values patchen
+
+Um Ecosystem-Core spezieller zu konfigurieren, kann eine Datei `.ecosystem-core-values-patch.yaml` im Root-Verzeichnis abgelegt werden.
+Ist diese Datei vorhanden, wird sie mit den Default-Values gemergt, wobei sich überschneidende Einträge überschrieben werden.
+
+Vorgehen:
+1. Template kopieren:
+   `cp .ecosystem-core-values-patch.yaml.template .ecosystem-core-values-patch.yaml`
+2. Inhalte anpassen (z. B. Backup & Monitoring aktivieren).
+3. Lokales Cluster neu erstellen mit `vagrant destroy -f && vagrant up`.
+   Die Datei wird automatisch in die Default-Values gemergt und angewendet.
+
+#### Longhorn-Values patchen
+
+Um Longhorn spezieller zu konfigurieren, kann eine Datei `.longhorn-values-patch.yaml` im Root-Verzeichnis abgelegt werden.
+Ist diese Datei vorhanden, wird sie mit den Default-Values gemergt, wobei sich überschneidende Einträge überschrieben werden.
+
+Vorgehen:
+1. Template kopieren:
+   `cp .longhorn-values-patch.yaml.template .longhorn-values-patch.yaml`
+2. Inhalte anpassen (z. B. Backup-Bucket konfigurieren).
+3. Lokales Cluster neu erstellen mit `vagrant destroy -f && vagrant up`.
+   Die Datei wird automatisch in die Default-Values gemergt und angewendet.
+
 #### Blueprint-Override
 
 Um weitere Dogus, oder spezielle Config zu installieren kann eine Datei `.blueprint-override.yaml` im Root-Verzeichnis abgelegt werden. 

docs/development/dev_box_en.md

@@ -120,6 +120,30 @@ If this is the case, no further steps are taken.
 This behavior can be disabled via the `forceUpgradeEcosystem` configuration in the `.vagrant.rb` file.
 Then the Helm release `ecosystem-core` and the blueprint will be updated with every `vagrant up`.
 
+#### Patch Ecosystem-Core values
+
+To customize the Ecosystem-Core configuration, a `.ecosystem-core-values-patch.yaml` file can be placed in the root directory.
+If this file exists, it is merged with the default values; overlapping entries are overwritten.
+
+Procedure:
+1. Copy the template:
+   `cp .ecosystem-core-values-patch.yaml.template .ecosystem-core-values-patch.yaml`
+2. Customize the content (e.g., enable backup & monitoring).
+3. Recreate the local cluster with `vagrant destroy -f && vagrant up`.
+   The file is automatically merged into the default values and applied.
+
+#### Patch Longhorn values
+
+To customize the Longhorn configuration, a `.longhorn-values-patch.yaml` file can be placed in the root directory.
+If this file exists, it is merged with the default values; overlapping entries are overwritten.
+
+Procedure:
+1. Copy the template:
+   `cp .longhorn-values-patch.yaml.template .longhorn-values-patch.yaml`
+2. Customize the content (e.g., configure a backup bucket).
+3. Recreate the local cluster with `vagrant destroy -f && vagrant up`.
+   The file is automatically merged into the default values and applied.
+
 #### Blueprint override
 
 To install additional Dogus or special configurations, a file named `.blueprint-override.yaml` can be stored in the root directory.
@@ -138,4 +162,4 @@ Notes:
 #### Cas configuration
 To ensure that cas Dogu forwards the logout URLs correctly locally, it is important
 that the key `allow_local_urls` is set to `‘true’` in the configuration for cas.
-This makes `*.localdomain` a valid domain for cas and the logout URLs are set correctly.
+This makes `*.localdomain` a valid domain for cas and the logout URLs are set correctly.

docs/development/test_lop-idp_en.md

@@ -0,0 +1,11 @@
+# Test LOP-IDP
+
+To test the new LOP-IDP and postfix components, copy the appropriate values patches like so:
+```bash
+cp docs/development/.lop-idp-blueprint-override.yaml .blueprint-override.yaml
+cp docs/development/.lop-idp-ecosystem-core-values-patch.yaml .ecosystem-core-values-patch.yaml
+```
+
+If you use mkcert, you have to set the `certificate/type` key to `external` in `.blueprint-override.yaml`.
+
+Due to [a bug in ecosystem-core](https://github.com/cloudogu/ecosystem-core/issues/64), a configmap with the name `postfix-config` will already exist and cause an error during the installation of postfix. Until it is fixed, it can for now be circumvented by deleting the configmap.