Our Kubernetes Configuration
Our Kubernetes solutions is fully integrated with our own API, and is installed on tested and proven hardware for Kubernetes. A cluster is not locked and can be managed either by tools like kubectl or using the Kubernetes API. Whether you choose shared hosting, Private Managed cluster or Private Self-Managed cluster they can all be integrated into your existing ASERGO infrastructure.
Kubernetes as a service (KaaS)
KaaS is the easiest and most cost-effective way to run your Kubernetes environment. Focus on running your applications while ASERGO takes full responsibility of managing, maintaining and updating all of the running components of the Kubernetes cluster.
- Kubernetes Dashboard
- Prometheus Metric Dashboard
- Customisable Network Ruleset
- Load Balancer
- Network Block Storage
Private Managed cluster
All you need to do is to manage your apps and your cluster environment, having absolutely no worries about security updates, patching or system upgrades.
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.
- API Server
- Controller Manager
- Kube Proxy
Private Self-managed cluster
Be in complete control of your cluster in all aspects. One of the biggest benefits of this solution is the overall flexibility it brings to your Kubernetes environment, but it requires experience and knowledge on how to manage, run and operate Kubernetes. Should you need our assistance, you are most welcome to contact our experts.
- Choose internal or external ectd cluster
- Free choice of CNI plugin
- Load Balancer
- Cluster Network
3 x master nodes
from 6 x worker nodes
60 cores/120 threads
480 GB RAM
no setup fee
Our Network & Topology Design
Network is an important part of Kubernetes and our clusters are 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. Policies is made of both egress and ingress rulesets and are applied to labels. Our clusters are also installed with a default pod isolation.
Flannel is 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 in IP tunneling or BGP peering.
All our solutions are based on the latest upstream release, fully open source and with no vendor lock-in.
Our Kubernetes runs on our own on-premises bare-metal servers and network infrastructure which enables you to integrate your Kubernetes with any of our products.
We have 2 kinds of Kubernetes nodes; Compute and Database
The core of our Kubernetes has not been altered. Toolkits such as kubectl or helm will work flawlessly with our cluster installations.
All Kubernetes nodes are connected together on an isolated network with 10Gbe+ connection.