Skip to content
Last update: January 10, 2022



Quorum-Kubernetes is a repository containing Kubernetes manifests and Helm charts that you can customize and deploy on a local cluster or in the cloud.


We recommend starting with the [playground] directory and working through the example setups before moving to the [dev] directory, and finally to the [prod] directory.

The dev and prod directories are identical in terms of what gets deployed, but differ in that the prod folder uses best practices to manage identity (Managed Identities in Azure and IAM in AWS), vaults (KeyVault in Azure and Secrets Manager in AWS), and CSI drivers.

All setups use monitoring and we recommend deploying the monitoring manifests or charts to get an overview of the network, nodes, and volumes; and you can create alerts accordingly. In addition, there’s an example configuration for Ingress and routes that you can customize to suit your requirements.

Cloud support

The repository currently supports AWS EKS and Azure AKS natively, and you can configure the provider in the values.yml file by setting provider to local, aws, or azure. You can also pass in extra configuration such as a KeyVault name.

The repository also contains Azure ARM templates and AWS eksctl templates to deploy the required base infrastructure.


When using multi-clusters, Kubernetes load balancers disallow TCP and UDP traffic on the same port, which inhibits discovery working natively for each pod. Use the following solutions to mitigate this limitation:

  • Disallow discovery and use static nodes to allow only TCP traffic. This isn’t an issue for load balancers or exposing nodes publicly.
  • If you need to use discovery, use something such as CNI which is supported by all major cloud providers, and the cloud templates already have CNI implemented.


With the traditional Kubelet networking mode, nodes get an IP from the virtual network subnet. Each node in turn uses NAT to configure the pods so that they reach other pods on the virtual network. This limits where they can reach but also more specifically what can reach them. For example, an external VM that must have custom routes doesn’t scale well.


CNI, on the other hand, allows every pod to get a unique IP directly from the virtual subnet, which removes this restriction. Therefore, it has a limit on the maximum number of pods that can be spun up, so you must plan ahead to avoid IP exhaustion.



You must enable CNI to use multi-cluster, or to connect external nodes to an existing Kubernetes cluster. To connect multiple clusters, they must each have different CIDR blocks to ensure no conflicts, and the first step is to peer the VPCs or VNets together and update the route tables. From that point on you can use static nodes and pods to communicate across the cluster.

The same setup also works to connect external nodes and business applications from other infrastructure, either in the cloud or on premise.


Back to top