cloudogu · meiserloh · Aug 5, 2025 · Aug 5, 2025 · Aug 5, 2025 · Aug 5, 2025
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -8,17 +8,42 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 *Breaking Change ahead!*
 
+### Added
+- [#121] Added use case to check if dogus actually use the desired version and config before completing the blueprint
+
 ### Changed
 - [#119] *breaking* sensitive dogu config can now only be referenced with secrets
-  - it was not safe to have these values in clear text in the blueprint
+    - it was not safe to have these values in clear text in the blueprint
 - [#119] we now support blueprint v2 CRs
-- [#121] health checks before and after applying the blueprint are now non-blocking
+- [#121] all health checks are now non-blocking
+- [#121] there are in general no steps anymore, which will block the reconciliation loop beyond some HTTP-Requests
+- [#121] *breaking* blueprints will now be executed as a continuous process
+    - the operator will now detect changes and will enforce the content of the blueprint
+- [#121] *breaking* the current state will now be reflected via conditions instead of the `statusPhase` field
+- [#121] *breaking* events were reworked, some events are now more general, some events got removed completely
+    - Note, that events are for humans. You should not compute them for automation as they have no consistency guarantees.
+- [#121] Upgrade to Golang v1.25.1
+- [#121] Upgrade Makefiles to v10.4.0
 
 ### Removed
 - [#119] *breaking* no support for v1 blueprint CRs anymore
-  - make sure to persist your blueprints before upgrading
-  - you need to transform your blueprints to the new v2 format yourself 
+    - make sure to persist your blueprints before upgrading
+    - you need to transform your blueprints to the new v2 format yourself
 - [#121] remove maintenance mode
+  - remove dependency to k8s-service-discovery (maintenance-mode was the reason for this dependency)
+- [#121] *breaking* dogus will not be restarted by the blueprint operator anymore
+    - this is now the responsibility of the dogu operator
+- [#121] *breaking* remove the ability to apply components (including self upgrade)
+  - Ecosystem-Core-Chart has now the resonsibility of components
+- [#121] *breaking* remove watching the health state of components in the ecosystem
+
+## [v2.8.0] - 2025-09-15
+### Changed
+- [#125] ignore nginx dependencies
+
+### Removed
+- [#125] component-dependency for component-oprator-crd
+  - it is replaced by a helm capabilities-check for the component CRD
 
 ## [v2.7.0] - 2025-07-17
 ### Fixed

diff --git a/Dockerfile b/Dockerfile
@@ -1,5 +1,5 @@
 # Build the manager binary
-FROM golang:1.24.3 AS builder
+FROM golang:1.25.1 AS builder
 
 WORKDIR /workspace
 
@@ -34,7 +34,7 @@ RUN make compile-generic
 FROM gcr.io/distroless/static:nonroot
 LABEL maintainer="[email protected]" \
       NAME="k8s-blueprint-operator" \
-      VERSION="2.7.0"
+      VERSION="2.8.0"
 
 WORKDIR /
 COPY --from=builder /workspace/target/k8s-blueprint-operator .

diff --git a/Jenkinsfile b/Jenkinsfile
@@ -12,9 +12,11 @@ github = new GitHub(this, git)
 changelog = new Changelog(this)
 Docker docker = new Docker(this)
 gpg = new Gpg(this, docker)
-goVersion = "1.24.3"
+goVersion = "1.25.1"
 Makefile makefile = new Makefile(this)
 
+componentOperatorVersion="1.10.0"
+
 // Configuration of repository
 repositoryOwner = "cloudogu"
 repositoryName = "k8s-blueprint-operator"
@@ -109,6 +111,11 @@ node('docker') {
             }
 
             stage('Deploy Manager') {
+                withCredentials([[$class: 'UsernamePasswordMultiBinding', credentialsId: 'harborhelmchartpush', usernameVariable: 'HARBOR_USERNAME', passwordVariable: 'HARBOR_PASSWORD']]) {
+                    k3d.helm("registry login ${registry} --username '${HARBOR_USERNAME}' --password '${HARBOR_PASSWORD}'")
+                    k3d.helm("install k8s-component-operator-crd oci://${registry}/k8s/k8s-component-operator-crd  --version ${componentOperatorVersion}")
+                    k3d.helm("registry logout ${registry}")
+                }
                 k3d.helm("install ${repositoryName} ${helmChartDir}")
             }
 

diff --git a/Makefile b/Makefile
@@ -1,9 +1,9 @@
 # Set these to the desired values
 ARTIFACT_ID=k8s-blueprint-operator
-VERSION=2.7.0
+VERSION=2.8.0
 IMAGE=cloudogu/${ARTIFACT_ID}:${VERSION}
-GOTAG=1.24.3
-MAKEFILES_VERSION=10.2.0
+GOTAG=1.25.1
+MAKEFILES_VERSION=10.4.0
 STAGE?=production
 
 

diff --git a/build/make/bats.mk b/build/make/bats.mk
@@ -9,7 +9,7 @@ BATS_SUPPORT=$(BATS_LIBRARY_DIR)/bats-support
 BATS_FILE=$(BATS_LIBRARY_DIR)/bats-file
 BATS_BASE_IMAGE?=bats/bats
 BATS_CUSTOM_IMAGE?=cloudogu/bats
-BATS_TAG?=1.11.0
+BATS_TAG?=1.12.0
 BATS_DIR=build/make/bats
 BATS_WORKDIR="${WORKDIR}"/"${BATS_DIR}"
 
@@ -18,15 +18,19 @@ unit-test-shell: unit-test-shell-$(ENVIRONMENT)
 
 $(BATS_ASSERT):
 	@git clone --depth 1 https://github.com/bats-core/bats-assert $@
+	@rm -rf $@/.git
 
 $(BATS_MOCK):
 	@git clone --depth 1 https://github.com/grayhemp/bats-mock $@
+	@rm -rf $@/.git
 
 $(BATS_SUPPORT):
 	@git clone --depth 1 https://github.com/bats-core/bats-support $@
+	@rm -rf $@/.git
 
 $(BATS_FILE):
 	@git clone --depth 1 https://github.com/bats-core/bats-file $@
+	@rm -rf $@/.git
 
 $(BASH_SRC):
 	BASH_SRC:=$(shell find "${WORKDIR}" -type f -name "*.sh")
@@ -49,10 +53,10 @@ unit-test-shell-local: $(BASH_SRC) $(PASSWD) $(ETCGROUP) $(HOME_DIR) buildTestIm
 		"${BATS_DIR}"/customBatsEntrypoint.sh make unit-test-shell-generic-no-junit
 
 unit-test-shell-generic:
-	@bats --formatter junit --output ${BASH_TEST_REPORT_DIR} ${TESTS_DIR}
+	@bats --report-formatter junit --formatter junit --output ${BASH_TEST_REPORT_DIR} ${TESTS_DIR}
 
 unit-test-shell-generic-no-junit:
-	@bats ${TESTS_DIR}
+	@bats --report-formatter junit --output ${BASH_TEST_REPORT_DIR} ${TESTS_DIR}
 
 .PHONY buildTestImage:
 buildTestImage:

diff --git a/build/make/bats/Dockerfile b/build/make/bats/Dockerfile
@@ -1,7 +1,7 @@
 ARG BATS_BASE_IMAGE
 ARG BATS_TAG
 
-FROM ${BATS_BASE_IMAGE:-bats/bats}:${BATS_TAG:-1.11.0}
+FROM ${BATS_BASE_IMAGE:-bats/bats}:${BATS_TAG:-1.12.0}
 
 # Make bash more findable by scripts and tests
 RUN apk add make git bash

diff --git a/build/make/bats/customBatsEntrypoint.sh b/build/make/bats/customBatsEntrypoint.sh
@@ -3,4 +3,11 @@ set -o errexit
 set -o nounset
 set -o pipefail
 
-"$@"
+targetReportDir="${PWD}"/target/shell_test_reports
+uidgid=1000:1000
+exitcode=0
+"$@" || exitcode=$?
+echo "Resetting file ownership to ${uidgid} in ${targetReportDir}/"
+chown -R ${uidgid} "${targetReportDir}"/*
+echo "exiting with code ${exitcode}"
+exit ${exitcode}
diff --git a/build/make/build.mk b/build/make/build.mk
@@ -3,7 +3,7 @@
 ADDITIONAL_LDFLAGS?=-extldflags -static
 LDFLAGS?=-ldflags "$(ADDITIONAL_LDFLAGS) -X main.Version=$(VERSION) -X main.CommitID=$(COMMIT_ID)"
 GOIMAGE?=golang
-GOTAG?=1.24
+GOTAG?=1.25
 GOOS?=linux
 GOARCH?=amd64
 PRE_COMPILE?=

diff --git a/build/make/k8s.mk b/build/make/k8s.mk
@@ -11,7 +11,7 @@ BINARY_YQ_4_VERSION?=v4.40.3
 BINARY_HELM = $(UTILITY_BIN_PATH)/helm
 BINARY_HELM_VERSION?=v3.13.0
 CONTROLLER_GEN = $(UTILITY_BIN_PATH)/controller-gen
-CONTROLLER_GEN_VERSION?=v0.14.0
+CONTROLLER_GEN_VERSION?=v0.19.0
 
 # Setting SHELL to bash allows bash commands to be executed by recipes.
 # Options are set to exit when a recipe line exits non-zero or a piped command fails.

diff --git a/build/make/static-analysis.mk b/build/make/static-analysis.mk
@@ -2,12 +2,12 @@
 
 STATIC_ANALYSIS_DIR=$(TARGET_DIR)/static-analysis
 GOIMAGE?=golang
-GOTAG?=1.24
+GOTAG?=1.25
 CUSTOM_GO_MOUNT?=-v /tmp:/tmp
 
 REVIEW_DOG=$(TMP_DIR)/bin/reviewdog
 LINT=$(TMP_DIR)/bin/golangci-lint
-LINT_VERSION?=v2.1.6
+LINT_VERSION?=v2.5.0
 # ignore tests and mocks
 LINTFLAGS=--tests=false --timeout 10m --issues-exit-code 0
 ADDITIONAL_LINTER=-E bodyclose -E containedctx -E contextcheck -E decorder -E dupl -E errname -E forcetypeassert -E funlen -E unparam

diff --git a/docs/operations/apply_blueprints_de.md b/docs/operations/apply_blueprints_de.md
@@ -3,35 +3,31 @@
 Sie können einen Blueprint anwenden, indem Sie eine `Blueprint`-Ressource auf den Cluster-Namespace anwenden, in dem das Cloudogu MultiNode EcoSystem läuft:
 
 ```yaml
-apiVersion: k8s.cloudogu.com/v1
+apiVersion: k8s.cloudogu.com/v2
 kind: Blueprint
 metadata:
+  labels:
+    app: ces
+    app.kubernetes.io/name: k8s-blueprint-lib
   name: my-blueprint
 spec:
-  # fügen Sie die blueprint.json hier ein
-  blueprint: |
-    {
-      "blueprintApi": "v2",
-      "dogus": [ ... ],
-      "components": [ ... ],
-      "config": {
-        "global": { ... },
-        "dogus": { ... }
-      }
-    }
-  # fügen Sie hier die blueprint-mask.json ein
-  blueprintMask: |
-    {
-      "blueprintMaskApi": "v1",
-      "blueprintMaskId": "my-blueprint-mask",
-      "dogus": [ ... ]
-    }
+  displayName: "Blueprint Sample v6.834"
+  # fügen Sie die blueprint hier ein
+  blueprint:
+    dogus: ...
+    config:
+      global: ...
+      dogus: ...
+  # fügen Sie hier die blueprint-mask ein
+  blueprintMask:
+    dogus: ...
 ```
 
 Das Dokument [Blueprint-Format](https://github.com/cloudogu/k8s-blueprint-lib/blob/develop/docs/operations/blueprintV2_format_de.md) beschreibt die Struktur des Blueprint im Detail.
 Blueprint-CR-Beispiele können dem [Sample-Repository](https://github.com/cloudogu/k8s-ecosystem-samples/tree/main/blueprints) entnommen werden. Wenn `k8s-blueprint-operator` korrekt installiert wurde, lässt sich dies z. B. so auf den Cluster anwenden:
 
 ```bash
-kubectl apply -n ecosystem -f k8s_v1_blueprint.yaml
+kubectl apply -n ecosystem -f k8s_v2_blueprint.yaml
 ```
 
+**Hinweis:** Pro Namespace ist nur ein Blueprint zulässig. Ändern Sie entweder das vorhandene Blueprint oder wenden Sie erneut ein `kubectl apply` mit demselben Blueprint-Namen an, um es zu aktualisieren.
diff --git a/docs/operations/apply_blueprints_en.md b/docs/operations/apply_blueprints_en.md
@@ -3,33 +3,30 @@
 You can apply a blueprint by applying a `Blueprint` resource to the cluster namespace where the Cloudogu MultiNode EcoSystem is running in:
 
 ```yaml
-apiVersion: k8s.cloudogu.com/v1
+apiVersion: k8s.cloudogu.com/v2
 kind: Blueprint
 metadata:
+  labels:
+    app: ces
+    app.kubernetes.io/name: k8s-blueprint-lib
   name: my-blueprint
 spec:
-  # put your blueprint.json here
-  blueprint: |
-    {
-      "blueprintApi": "v2",
-      "dogus": [ ... ],
-      "components": [ ... ],
-      "config": {
-        "global": { ... },
-        "dogus": { ... }
-      }
-    }
-  # put your blueprint-mask.json here
-  blueprintMask: |
-    {
-      "blueprintMaskApi": "v1",
-      "blueprintMaskId": "my-blueprint-mask",
-      "dogus": [ ... ]
-    }
+  displayName: "Blueprint Sample v6.834"
+  # put your blueprint here
+  blueprint: 
+    dogus: ...
+    config:
+      global: ...
+      dogus: ...
+  # put your blueprint-mask here
+  blueprintMask:
+      dogus: ...
 ```
 The document [blueprint format](https://github.com/cloudogu/k8s-blueprint-lib/blob/develop/docs/operations/blueprintV2_format_en.md) describes the structure of the Blueprint in detail.
 You may see examples of Blueprint-CRs in the [sample repository](https://github.com/cloudogu/k8s-ecosystem-samples/tree/main/blueprints). With `k8s-blueprint-operator` properly being installed, you can apply it to the cluster like this:
 
 ```bash
-kubectl apply -n ecosystem -f k8s_v1_blueprint.yaml
+kubectl apply -n ecosystem -f k8s_v2_blueprint.yaml
 ```
+
+**Note:** Only one blueprint is permitted per namespace. Either change the existing one or apply with the same name to update it.
diff --git a/docs/operations/health_checks_de.md b/docs/operations/health_checks_de.md
@@ -3,36 +3,13 @@
 Vor und nach dem Anwenden des Blueprints wird gewartet, dass das Ecosystem healthy ist.
 Dabei wird folgendes geprüft:
 - Health aller Dogus anhand der Dogu-CRs
-- Health aller Components anhand der Component-CRs
-- Überprüfung, ob alle notwendigen Components installiert sind, die für das Blueprint gebraucht werden
-
-Die Health-Checks verwenden einen eingebauten Retry. 
-Timeout und Check-Interval lassen sich dafür in der [Health-Config](#health-config) festlegen.
+- Überprüfung, ob alle Dogus bereits die neueste Version und Konfiguration verwenden
 
 ## Health ignorieren
 
 Die Health-Checks vor der Ausführung des Blueprints können deaktiviert werden:
 - für Dogus, wenn `spec.ignoreDoguHealth` auf `true` gesetzt wird,
-- für Components, wenn `spec.ignoreComponentHealth` auf `true` gesetzt wird.
 
 So ist es möglich, per Blueprint Fehler an Dogus und Komponenten zu beheben.
 Für ein Dogu-Upgrade muss ein Dogu allerdings healthy sein, um Pre-Upgrade-Skripte ausführen zu können.
 Das Ignorieren der Dogu-Health kann also zu Folgefehlern während der Ausführung des Blueprints führen.
-
-## Health-Config
-
-Die Health-Konfiguration kann im Feld `valuesYamlOverwrite` der Komponenten-CR des Blueprint-Operators überschrieben werden.
-Folgendes Beispiel zeigt die möglichen Einstellungen mit ihrer Default-Konfiguration:
-
-```yaml
-valuesYamlOverwrite: |
-  healthConfig:
-    components:
-      required: # These components are required for health checks to succeed.
-      - name: k8s-dogu-operator
-      - name: k8s-service-discovery
-      - name: k8s-component-operator
-    wait: # Define timeout and check-interval for the ecosystem to become healthy.
-      timeout: 10m
-      interval: 10s
-```
diff --git a/docs/operations/health_checks_en.md b/docs/operations/health_checks_en.md
@@ -3,36 +3,13 @@
 Before and after applying the blueprint, the ecosystem is checked to ensure that it is healthy.
 The following is checked:
 - Health of all Dogus based on the Dogu-CRs
-- Health of all components based on the component CRs
-- Check whether all necessary components required for the blueprint are installed
-
-The health checks use a built-in retry.
-The timeout and check interval can be defined in the [Health-Config](#health-config).
+- Check whether all Dogus already use the latest version and configuration
 
 ## Ignoring health
 
 Upfront health checks can be deactivated:
 - for Dogus, if `spec.ignoreDoguHealth` is set to `true`,
-- for components, if `spec.ignoreComponentHealth` is set to `true`.
 
 This makes it possible to fix errors on Dogus and components via Blueprint.
 For a Dogu upgrade, however, a Dogu must be healthy in order to be able to execute pre-upgrade scripts.
 Ignoring the dogu health can therefore lead to subsequent errors during the execution of the blueprint.
-
-## Health-Config
-
-The health configuration can be overwritten in the `valuesYamlOverwrite` field of the component CR of the blueprint operator.
-The following example shows the possible settings with their default configuration:
-
-```yaml
-valuesYamlOverwrite: |
-  healthConfig:
-    components:
-      required: # These components are required for health checks to succeed.
-      - name: k8s-dogu-operator
-      - name: k8s-service-discovery
-      - name: k8s-component-operator
-    wait: # Define timeout and check-interval for the ecosystem to become healthy.
-      timeout: 10m
-      interval: 10s
-```