---
title: "Replatform to STACKIT: Spring Boot on SKE and PostgreSQL Flex"
description: "Replatform Spring Boot and PostgreSQL to SKE and PostgreSQL Flex: prepare source and target, rehearse the data migration, cut over, validate, and stabilize."
scfTrail:
  tags: [ "replatform", "spring-boot", "postgresql", "ske", "terraform", "cutover", "gateway-api", "observability" ]
  maintainers:
    - user: "lukas.weberruss"
      role: true
      website: true
  steps:

    - style: "chairlift"
      id: "confirm-replatform"
      title: "Replatform Strategy and Tools"
      trailContext: "Confirm the two deliberate substitutions: a VM service becomes a Kubernetes Deployment, and VM-local PostgreSQL becomes PostgreSQL Flex. Preserve the Spring Music JAR and business behavior; this is Replatform rather than VM Rehost or application Refactor."
      pageId: "migration/design-and-mobilize/design/replatform/#understanding-replatform"
      imageSrc: "migration/files/r-strategy-method.svg"
      imageAlt: "R-strategy method placing Replatform between Rehost and Refactor"

    - style: "chart"
      id: "target-architecture"
      title: "Target Runtime Architecture"
      trailContext: "Review the implemented one-worker reference: the same JAR on SKE, a ClusterIP Service behind Envoy Gateway, managed DNS, PostgreSQL Flex, and Observability. Distinguish this tested topology from optional high-availability and integration-service extensions."
      assetId: "migration/assetcontainer/stackit/architecture-spring-boot-kubernetes-paas-data-object-storage#architecture-diagram"

    - style: "rocket"
      id: "reference-implementation"
      title: "Reference Implementation"
      trailContext: "Move from framework principles to the maintained Spring Boot Kubernetes repository. Use its reviewed Terraform, Helm charts, pinned JAR and images, migration scripts, and validation as the technical source throughout the remaining journey."
      assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#reference-implementation"

    - style: "stairs"
      id: "prepare-workspace"
      title: "Prepare the Lab and Repositories"
      trailContext: "Confirm the prepared Linux lab, PostgreSQL tools, approved repository revisions, credentials, and project prerequisites before generating sample data. Stop if the reviewed implementation is not available; never substitute an unverified default branch."
      assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#prepare-the-walkthrough-workspace"

    - style: "shield"
      id: "source-target-readiness"
      title: "Prepare Source Evidence"
      trailContext: Capture and validate the source dump, manifest and data boundary before target provisioning. Keep the source and isolated test data unambiguous.
      assetId: migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#prepare-source-evidence

    - style: "stairs"
      id: "deploy-and-check-target"
      title: "Configure Target Inputs"
      trailContext: "Select and review SKE, Flex, Gateway, DNS and Observability before provisioning. Keep HPA, load generation and the obsolete direct-import Job disabled."
      assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#minimal-target-configuration"
    - style: hut
      id: provision-target
      title: Provision the Target
      trailContext: Review target inputs and the infrastructure plan, provision the resources, and retain the results before migration rehearsal.
      assetId: migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#provision-the-target

    - style: "shield"
      id: "database-access"
      title: "Verify Database Access Boundaries"
      trailContext: "Check SKE egress ACLs, the in-cluster migration path, credential protection, and the limits of sslmode=require before restoring any data."
      assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#access-control-and-temporary-migration-acl-extension"

    - style: "stairs"
      id: "validate-target"
      title: "Configure kubectl and Validate the Target"
      trailContext: "Export a private, short-lived kubeconfig and check Deployment, Gateway, HTTPRoute, DNS, and application readiness before rehearsal. Remove the local kubeconfig after use."
      assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#validation-with-kubectl"

    - style: "chart"
      id: "inspect-telemetry"
      title: "Verify the Telemetry Path"
      trailContext: "Open the managed dashboard and verify actual application and database scrape results. Missing telemetry blocks trustworthy acceptance even when the application responds."
      assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#database-metrics-visibility-in-observability"

    - style: "stairs"
      id: "rehearse-and-approve"
      title: "Rehearse and Approve"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#rehearse-the-migration"
      right:
        - assetId: "migration/assetcontainer/stackit/runbook-replatform-spring-boot#pre-migration-checks"

    - style: "rocket"
      id: "execute-cutover"
      title: "Execute the Cutover"
      trailContext: "Freeze source writes and run the explicitly confirmed workflow. The script stops the application, protects and proves the target backup, imports the source transactionally, validates data, and restores replicas. The operator owns traffic switching and business release."
      assetId: "migration/assetcontainer/stackit/runbook-replatform-spring-boot#run-plan-cutover-window"

    - style: "shield"
      id: "validate-or-rollback"
      title: "Validate or Roll Back"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/runbook-replatform-spring-boot#validation-checklist"
      right:
        - assetId: "migration/assetcontainer/stackit/runbook-replatform-spring-boot#rollback-criteria-and-steps"

    - style: "summit"
      id: "stabilize-and-handover"
      title: "Stabilize the Reference Implementation"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/runbook-replatform-spring-boot#handover-to-operations"
      right:
        - assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#backup-and-recovery-boundary"

    - style: "chart"
      id: "reference-results"
      title: "Verified Results and Remaining Limits"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#what-this-asset-demonstrates"
      right:
        - assetId: "migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform#out-of-scope"

    - style: "summit"
      id: "optimize-framework"
      title: "Stabilize and Optimize"
      trailContext: "Return to the Migration Framework's Optimize loop: collect representative operating evidence, identify the limiting layer, implement one controlled change, and validate reliability, performance, and cost before keeping it."
      pageId: "migration/migrate/optimize/overview/#understanding-the-optimize-module"

    - style: "chart"
      id: "optimize-reference-implementation"
      title: "Continue the Same Reference Implementation"
      trailContext: "Keep the same repository, deployment, database, and monitoring baseline. Optimization follows acceptance and stabilization; it is not an extra experiment inside the cutover window."
      assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#continue-the-reference-implementation"

    - role: "sub"
      id: "optimize-target"
      title: "Select an Optimization Candidate"
      trailContext: "Use the eight-panel dashboard as a starting point, verify actual scrape health, and correlate cluster, application, and database pressure with business evidence. Do not infer zero load from fallback values or production SLOs from mean request duration."
      assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#observability-decision-dashboard"

    - style: "chart"
      id: "optimize-database"
      title: "Right-size PostgreSQL Flex"
      trailContext: "Distinguish connection, query, lock, and storage pressure before selecting a supported Flex flavor or storage change. Review replacement and reversibility constraints, retain recovery evidence, and never treat an infrastructure replacement as a routine data rollback."
      assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#postgresql-flex-rightsizing-and-tuning"

    - style: "chart"
      id: "optimize-pod-budget"
      title: "Right-size the Pod Budget"
      trailContext: "Compare JVM heap, non-heap memory, CPU throttling, startup behavior, and exporter overhead before editing the Deployment resource budgets. Schedule the rollout and validate application and data behavior against the baseline."
      assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#pod-resources-and-jvm-budget"

    - style: "stairs"
      id: "optimize-scaling"
      title: "Qualify Pod and Worker Scaling"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#pod-autoscaling-control-loop"
      right:
        - assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#cluster-and-platform-rightsizing"

    - style: "stairs"
      id: "optional-hpa-experiment"
      title: "Optional: Configure and Inspect HPA"
      trailContext: "Only after stabilization and the end of migration or rollback operations, run a separately approved scaling experiment. Qualify per-pod telemetry and replica ownership first; these commands are not part of the validated migration baseline."
      assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#pod-autoscaling-configuration"

    - style: "shield"
      id: "optimize-acceptance"
      title: "Validate the Optimization"
      trailContext: "Compare the changed system with the accepted baseline over the agreed observation window. Keep only demonstrated improvements, use the approved reversal or recovery path when criteria regress, and feed the result into future migration waves."
      assetId: "migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing#rollback-and-acceptance"

  presentations:

    - id: "technical-replatform-path"
      label: "Technical walkthrough"
      description: "Reproduce the sample in a prepared lab: repositories, source dump, target setup, checks, rehearsal, cutover, recovery, and optional optimization."
      launch: true
      preset: "standard"
      fullscreen: true
      steps:
        - confirm-replatform
        - target-architecture
        - reference-implementation
        - prepare-workspace
        - source-target-readiness
        - deploy-and-check-target
        - provision-target
        - database-access
        - validate-target
        - inspect-telemetry
        - rehearse-and-approve
        - execute-cutover
        - validate-or-rollback
        - stabilize-and-handover
        - reference-results
        - id: optimize-framework
          notes: Optional follow-up after stabilization, not part of the cutover. HPA and capacity changes require their own approval and validation.
        - optimize-reference-implementation
        - id: optimize-target
          role: sub
        - optimize-database
        - optimize-pod-budget
        - optimize-scaling
        - optional-hpa-experiment
        - optimize-acceptance
      default: true
source_url: "https://framework.stackit.cloud/migration/trails/stackit/spring-boot-postgresql-replatform-technical-walkthrough/"
source_file: "docs/migration/trails/stackit/spring-boot-postgresql-replatform-technical-walkthrough.mdx"
---

## Steps

### 1. Replatform Strategy and Tools

Stage: `chairlift`

Confirm the two deliberate substitutions: a VM service becomes a Kubernetes Deployment, and VM-local PostgreSQL becomes PostgreSQL Flex. Preserve the Spring Music JAR and business behavior; this is Replatform rather than VM Rehost or application Refactor.

Page: [/migration/design-and-mobilize/design/replatform/#understanding-replatform](/migration/design-and-mobilize/design/replatform/#understanding-replatform) — source: [/raw/migration/design-and-mobilize/design/replatform.md](/raw/migration/design-and-mobilize/design/replatform.md), section `#understanding-replatform`

### 2. Target Runtime Architecture

Stage: `chart`

Review the implemented one-worker reference: the same JAR on SKE, a ClusterIP Service behind Envoy Gateway, managed DNS, PostgreSQL Flex, and Observability. Distinguish this tested topology from optional high-availability and integration-service extensions.

Asset: [/migration/assetcontainer/stackit/architecture-spring-boot-kubernetes-paas-data-object-storage/#architecture-diagram](/migration/assetcontainer/stackit/architecture-spring-boot-kubernetes-paas-data-object-storage/#architecture-diagram) — source: [/raw/migration/assetcontainer/stackit/architecture-spring-boot-kubernetes-paas-data-object-storage.md](/raw/migration/assetcontainer/stackit/architecture-spring-boot-kubernetes-paas-data-object-storage.md), section `#architecture-diagram`

### 3. Reference Implementation

Stage: `rocket`

Move from framework principles to the maintained Spring Boot Kubernetes repository. Use its reviewed Terraform, Helm charts, pinned JAR and images, migration scripts, and validation as the technical source throughout the remaining journey.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#reference-implementation](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#reference-implementation) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#reference-implementation`

### 4. Prepare the Lab and Repositories

Stage: `stairs`

Confirm the prepared Linux lab, PostgreSQL tools, approved repository revisions, credentials, and project prerequisites before generating sample data. Stop if the reviewed implementation is not available; never substitute an unverified default branch.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#prepare-the-walkthrough-workspace](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#prepare-the-walkthrough-workspace) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#prepare-the-walkthrough-workspace`

### 5. Prepare Source Evidence

Stage: `shield`

Capture and validate the source dump, manifest and data boundary before target provisioning. Keep the source and isolated test data unambiguous.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#prepare-source-evidence](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#prepare-source-evidence) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#prepare-source-evidence`

### 6. Configure Target Inputs

Stage: `stairs`

Select and review SKE, Flex, Gateway, DNS and Observability before provisioning. Keep HPA, load generation and the obsolete direct-import Job disabled.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#minimal-target-configuration](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#minimal-target-configuration) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#minimal-target-configuration`

### 7. Provision the Target

Stage: `hut`

Review target inputs and the infrastructure plan, provision the resources, and retain the results before migration rehearsal.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#provision-the-target](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#provision-the-target) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#provision-the-target`

### 8. Verify Database Access Boundaries

Stage: `shield`

Check SKE egress ACLs, the in-cluster migration path, credential protection, and the limits of sslmode=require before restoring any data.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#access-control-and-temporary-migration-acl-extension](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#access-control-and-temporary-migration-acl-extension) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#access-control-and-temporary-migration-acl-extension`

### 9. Configure kubectl and Validate the Target

Stage: `stairs`

Export a private, short-lived kubeconfig and check Deployment, Gateway, HTTPRoute, DNS, and application readiness before rehearsal. Remove the local kubeconfig after use.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#validation-with-kubectl](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#validation-with-kubectl) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#validation-with-kubectl`

### 10. Verify the Telemetry Path

Stage: `chart`

Open the managed dashboard and verify actual application and database scrape results. Missing telemetry blocks trustworthy acceptance even when the application responds.

Asset: [/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#database-metrics-visibility-in-observability](/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform/#database-metrics-visibility-in-observability) — source: [/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md](/raw/migration/assetcontainer/stackit/replatform-automation-spring-boot-vm-to-kubernetes-terraform.md), section `#database-metrics-visibility-in-observability`

### 11. Rehearse and Approve

Stage: `stairs`

### 12. Execute the Cutover

Stage: `rocket`

Freeze source writes and run the explicitly confirmed workflow. The script stops the application, protects and proves the target backup, imports the source transactionally, validates data, and restores replicas. The operator owns traffic switching and business release.

Asset: [/migration/assetcontainer/stackit/runbook-replatform-spring-boot/#run-plan-cutover-window](/migration/assetcontainer/stackit/runbook-replatform-spring-boot/#run-plan-cutover-window) — source: [/raw/migration/assetcontainer/stackit/runbook-replatform-spring-boot.md](/raw/migration/assetcontainer/stackit/runbook-replatform-spring-boot.md), section `#run-plan-cutover-window`

### 13. Validate or Roll Back

Stage: `shield`

### 14. Stabilize the Reference Implementation

Stage: `summit`

### 15. Verified Results and Remaining Limits

Stage: `chart`

### 16. Stabilize and Optimize

Stage: `summit`

Return to the Migration Framework's Optimize loop: collect representative operating evidence, identify the limiting layer, implement one controlled change, and validate reliability, performance, and cost before keeping it.

Page: [/migration/migrate/optimize/overview/#understanding-the-optimize-module](/migration/migrate/optimize/overview/#understanding-the-optimize-module) — source: [/raw/migration/migrate/optimize/overview.md](/raw/migration/migrate/optimize/overview.md), section `#understanding-the-optimize-module`

### 17. Continue the Same Reference Implementation

Stage: `chart`

Keep the same repository, deployment, database, and monitoring baseline. Optimization follows acceptance and stabilization; it is not an extra experiment inside the cutover window.

Asset: [/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#continue-the-reference-implementation](/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#continue-the-reference-implementation) — source: [/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md](/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md), section `#continue-the-reference-implementation`

### 18. Select an Optimization Candidate

Use the eight-panel dashboard as a starting point, verify actual scrape health, and correlate cluster, application, and database pressure with business evidence. Do not infer zero load from fallback values or production SLOs from mean request duration.

Asset: [/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#observability-decision-dashboard](/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#observability-decision-dashboard) — source: [/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md](/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md), section `#observability-decision-dashboard`

### 19. Right-size PostgreSQL Flex

Stage: `chart`

Distinguish connection, query, lock, and storage pressure before selecting a supported Flex flavor or storage change. Review replacement and reversibility constraints, retain recovery evidence, and never treat an infrastructure replacement as a routine data rollback.

Asset: [/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#postgresql-flex-rightsizing-and-tuning](/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#postgresql-flex-rightsizing-and-tuning) — source: [/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md](/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md), section `#postgresql-flex-rightsizing-and-tuning`

### 20. Right-size the Pod Budget

Stage: `chart`

Compare JVM heap, non-heap memory, CPU throttling, startup behavior, and exporter overhead before editing the Deployment resource budgets. Schedule the rollout and validate application and data behavior against the baseline.

Asset: [/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#pod-resources-and-jvm-budget](/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#pod-resources-and-jvm-budget) — source: [/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md](/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md), section `#pod-resources-and-jvm-budget`

### 21. Qualify Pod and Worker Scaling

Stage: `stairs`

### 22. Optional: Configure and Inspect HPA

Stage: `stairs`

Only after stabilization and the end of migration or rollback operations, run a separately approved scaling experiment. Qualify per-pod telemetry and replica ownership first; these commands are not part of the validated migration baseline.

Asset: [/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#pod-autoscaling-configuration](/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#pod-autoscaling-configuration) — source: [/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md](/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md), section `#pod-autoscaling-configuration`

### 23. Validate the Optimization

Stage: `shield`

Compare the changed system with the accepted baseline over the agreed observation window. Keep only demonstrated improvements, use the approved reversal or recovery path when criteria regress, and feed the result into future migration waves.

Asset: [/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#rollback-and-acceptance](/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing/#rollback-and-acceptance) — source: [/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md](/raw/migration/assetcontainer/stackit/optimize-replatformed-spring-boot-kubernetes-rightsizing.md), section `#rollback-and-acceptance`