Link Search Menu Expand Document

Using the Move2Kube UI


Similar to the command line tool, Move2Kube Web-UI can also be used to do the transformation. The Web-UI has all the capabilities that are there in the command line tool. This document explains the steps to bring up the UI and backend using docker and use it for transformation.


  1. Install Docker.

  2. We will use language-platforms sample. The language-platforms file has a combination of multiple applications in different languages (Java, Go, Python, Ruby, etc.) which needs to be containerized and then put into Kubernetes.

Steps to use the UI to do a transformation

  1. Download the language platforms sample as a zip.
     $ curl | bash -s -- -d samples/language-platforms -r move2kube-demos -z
     $ ls
  2. Do a docker run --rm -it -p 8080:8080
     $ docker run --rm -it -p 8080:8080
     INFO[0000] Starting Move2Kube API server at port: 8080

    It starts a container using the Move2Kube UI image on port 8080.

     # Optionally if you need persistence then mount the current directory:
     $ docker run --rm -it -p 8080:8080 -v "${PWD}/move2kube-api-data:/move2kube-api/data"
     # And if you also need more advanced features of Move2Kube then mount the docker socket. This will allow Move2Kube to run container based transformers:
     $ docker run --rm -it -p 8080:8080 -v "${PWD}/move2kube-api-data:/move2kube-api/data" -v //var/run/docker.sock:/var/run/docker.sock
  3. Open http://localhost:8080 in your browser.

  4. Create a new workspace Workspace 1 by clicking on the New Workspace button.

    No workspaces Create workspace New workspace

  5. Scroll down and create a new project Project 1 by clicking on the New Project button.

    No projects Create project New project

  6. Scroll down to the Project inputs section and upload the file which we downloaded earlier in this tutorial and wait for it to finish uploading.

    No project inputs Create project input New project input

  7. Now scroll down to the Plan section and click on the Start Planning button. Wait for the plan to get generated. It takes about three to five minutes to generate the plan.

    No plan Start planning

  8. Once the plan is generated you can scroll to see the different services. The plan is in YAML format. If you edit the plan don’t forget to click Save.

    Planning finished

  9. Now scroll down to Outputs section and click on the Start Transformation button.

    No outputs

  10. Move2Kube will ask some questions to aid in the transformation process.

    Start transformation

    For the question about container registry, specify the container registry where you want to push the images. Transformation QA

    Same for the question about container registry namespace. Transformation QA

    If your container registry requires authentication for pulling images, then specify that in the question about container registry login. Transformation QA

    For the question about ingress host, specify the hostname of the Kubernetes cluster. If you are deploying to Minikube then specify localhost as the hostname and leave the TLS secret blank. Transformation QA Transformation QA

    For all other questions we can keep clicking the Next button and go with the default answers.

  11. After the questions are finished wait a few minutes for it to finish processing. Once it’s done, you can click on the output to download the generated artifacts as a zip file (here, extract it and browse them. The applications can now be deployed to Kubernetes using these generated artifacts.

    Transformation finished Download output Exploring the output

Now we can build and push the container images and deploy to Kubernetes using the output we downloaded.
The steps for doing that are same as for the CLI tutorial.


We have seen how easy it is to do a transformation using the UI. All the features of the Move2Kube CLI are available through the UI as well. In addition, the UI can be hosted on a common server and used by different teams using different workspaces. It also has authentication and authorization capabilities to restrict access to particular workspaces.