Deploy, scale & manage with Kubernetes

Private managed cluster
Self-managed Vanilla K8s cluster

Kubernetes as a Service (KaaS)

KaaS is by far the easiest and most cost effective way to run your Kubernetes environment. Sign up for a K8s Namespace and deploy all the pods you need. Focus on running your applications while ASERGO take full responsibility of managing and maintaining the tough stuff such as running the cluster and more.

Our KaaS environment include various essential services such as; K8s Dashboard, Prometheus monitoring, basic network rule set, external load balancer and integration to our network block storage.

Private Managed Cluster

If your business is to focus on your applications rather than spending time of maintaining your private cluster, this is for you. We will make a vanilla K8s private cluster available to you, while our experienced K8s experts will be responsible for maintaining the core components of the cluster.

Components include:

  • etcd,
  • kubelet
  • API Server
  • Controller Manager
  • Scheduler
  • Kube Proxy
  • CoreDNS and more.

All you need to do is managing your apps and your cluster environment, having absolutely no worries about security updates, patching or system upgrades.

Self-managed Vanilla K8s cluster

Having a vanilla K8s cluster you are on your own and you are responsible for managing everything right down to the core of your cluster. You are in complete control of your cluster in all aspects

It goes without saying that this option requires experience and knowledge on how to manage, run and operate a k8s cluster.

ASERGO is responsible for running and maintaining the infrastructure embracing your environment.

Should you need our advice, troubleshooting or sparring, you are most welcome to contact us and talk to our Kubernetes experts. This service is charged a token amount of €40 per half hour.

Network / Topology Design

Network is an important part of Kubernetes. An ASERGO cluster is installed with Canal. Canal uses Flannel as a base and applies Calico's network policy ruleset.

Using network policies will give you full control over your network flow. Our clusters are installed with a default pod isolation, this means traffic to and from pods needs to be explicit defined. Policies is made of both egress and ingress rulesets and are applied to labels.


Flannel a simple layer 2 fabric specific designed for Kubernetes. It will forward the traffic from the host to pods with the help of VXLAN or UDP overlay.
This fabric is focused on networking


Calico is a flat layer 3 network fabric designed for container networks. It provides communication with IP encapsulation or network address translation for better performance and easier troubleshooting. Calico uses IP-inIP tunneling or BGP peering.

Nice to know

Dedicated Hardware

We have 2 kind of Kubernetes nodes; Compute or database. Compute nodes is the common node. If you need to run databases in Kubernetes, which needs local storage and low disk IO have we designed a database node for the purpose.


All Kubernetes nodes are connected together on an isolated network with 10Gbe+ connection.

Pure Kubernetes

No matter which Kubernetes solution you choose, the core of Kubernetes has not been altered. This means toolkits such as kubectl or helm will work flawless with our cluster installations.