This topic describes how developers migrate application configurations from Swarm to Kubernetes after O&M engineers have migrated cluster configurations. The following steps are involved: set up the environment, preprocess and convert Swarm compose files, deploy Kubernetes resource files, manually migrate application configurations that cannot be automatically converted, and debug the application to fix potential issues.

Concept differences

Swarm and Kubernetes both use various concepts when it comes to applications, services, and access methods. For more information about the differences between these concepts, see Concepts.


You have an application that needs to be migrated from Swarm to Kubernetes. You have set up the target Kuberenetes cluster. This topic uses swarm-piggymetrics as the sample application and migrates its configurations to cluster k8s-piggymetrics-cluster.

Based on PiggyMetrics, swarm-piggymetrics is an application built on a microservice architecture. PiggyMetrics is a Spring Cloud project on GitHub. In this example, the application has been improved to include more Swarm parameters. This helps demonstrate the complete procedure of migrating application configurations.


  1. Set up the environment.
  2. Preprocess Swarm Compose files.
  3. Convert Swarm Compose files.
  4. Deploy Kubernetes resource files.
  5. Manually migrate application configurations.
  6. Check the application status.
  7. Migrate log configurations of applications.

Related topics

For more information about migration related questions, see Troubleshooting.

For more information about parameters, see Application configuration parameters, Application release parameters, Network configuration parameters, and Log configuration parameters.