Skip to main content

WaveMaker Integrates with DigitalOcean Kubernetes for App Deployments

· 5 min read

WaveMaker platform's one-click deploy feature now enables applications to be deployed to Kubernetes clusters on Digital Ocean cloud.

You can configure the deployment topology as per your requirement and then with a single button click, WaveMaker platform's deploy feature generates the docker files needed to build images, generates the K8S YAML files needed for deployment and triggers the K8S APIs for deployment. Customer's don't have to write even a single line of K8S YAML file!!

WaveMaker offers a pre-defined set of delivery phases which enables team a progression through Demo, Stage and Live phase. This let's you thoroughly verify your apps before taking them to the live environment.

Demo phase uses WaveMaker's internal cloud. But the Stage and Live phases need to be configured to use your own AWS, Azure or GCP accounts. To this list of cloud providers to choose from, we are now adding Digital Ocean. This is the first Kubernetes based cloud provider supported by the WaveMaker Platform.

Let us introduce you to the DigitalOcean Kubernetes cluster and walk you through the benefits of a Kubernetes based cloud provider and its deployments.

Introduction to DigitalOcean Kubernetes

DigitalOcean Kubernetes (DOKS) is a managed Kubernetes service that lets you deploy Kubernetes clusters without the complexities of handling the control plane and containerized infrastructure. Clusters are compatible with standard Kubernetes toolchains and integrate natively with DigitalOcean Load Balancers and block storage volumes.

Why to choose Kubernetes based deployments?

Before getting to the "why", let's understand first what basically is a kubernetes based deployment? To understand the scope of this, let us first go through and compare the different era's of app deployments:

Traditional deployment era: Every application was run on a physical server. Since no boundaries were defined for the applications in the physical server, there were instances when one application would take up all the resources resulting in all other applications to underpeform. Scaling of applications was difficult as resources were underutilized.

Virtualized deployment era: Virtualization being the solution for shortcomings of the traditional deployments, also provided security of application's information as the applications were isolated between the VMs.

Container deployment era: Containers, as we all know, are considered as lightweight systems as they are decoupled from the underlying infrastructure and at the same time have their own fileSystem, CPU, memory, process space etc. to maintain isolation between applications running. Containerized based deployments became popular due to multiple benefits like resource isolation, resource utilization etc.


So then why do you need Kubernetes and what can be done with it?

Kubernetes deployments, you can say, are nothing but containerized deployments only, with Kubernetes providing you with a framework to manage container resources, scaling and failover for your application. For ex: if a container goes down, another container needs to start. Wouldn’t it be easier if this behavior was handled by a system? Kubernetes helps us with this process and many other features that are good for the infrastructures!

  • Auto Scaling,
  • Self healing,
  • Service Discovery,
  • Storage orchestration are few among the features that the application developer receives on adapting to Kubernetes based cloud provider deployments.

Now that we understand the benefits of a Kubernetes based deployment, let us understand how WaveMaker platform simplifies the deployment process.

What does an application developer need to deploy his app on DigitalOcean Cloud?

To deploy your application on DigitalOcean cloud, all you would need is a DigitalOcean account.

There are two stages involved for setting up the live/stage phase of the release pipeline with the DigitalOcean cloud provider:

  • Configuration of DigitalOcean cluster
  • Deployment of application to DigitalOcean cluster


Configuration of DigitalOcean cluster

After choosing DigitalOcean Provider from the list of providers, an access token needs to be provided.

To spin up a new cluster in your account some configuration details need to be provided as well:

  • cluster region,
  • cluster name and
  • cluster capacity.


After providing these details WaveMaker spins up a new cluster in your Digital Ocean account.

Alternatively, you may well choose to use an existing cluster already present in your account. screenshot

This cluster is then associated with the live/stage phase of the release pipeline.

Deployment of application to DigitalOcean cluster

Once the live/stage phase of the release pipeline is associated with a cluster in DigitalOcean account, you are now ready to deploy.


There is no need to write K8S specific yaml files or build any app images!

WaveMaker automatically generates dockerfiles, builds a docker image, generates the K8S manifest files and deploys the application to cluster using K8S API's.

Also, the app memory and number of pod replicas are completely configurable from UI.


The cluster creation process and the app deployment process are executed as jobs and run in the background, allowing you to continue with your development while the cluster creates or the application deploys.

What happens post the app is deployed?

Now post deployment, the app developer is returned with a Service URL which is the URL of the deployed application.


Not only is the application deployed on a kubernetes cluster, but the platform also returns deployment specific information like

  • namespace at which the application has been deployed,
  • the image used for the deployment process,
  • the cluster version and
  • worker node size being used etc.

You can use the kubectl commands with the associated kubernetes cluster or debug the image in the associated registry.



Go ahead and try out your app's first ever kubernetes deployment and let us know your experience!!