Support Matrix

Kubernetes Fury Distribution Support Matrix documentation

SIGHUP engineering team has designed this distribution to be able to be installed on top of any Kubernetes (Upstream) Cluster. The current version of this distribution (v1) has been tested across three different Kubernetes Cluster Versions.

Every core module that is part of this distribution has its own tests across these three Kubernetes Upstream versions. This way we can ensure:

  • Every module is compatible with three different Kubernetes Cluster by itself.
  • All core modules (as a Distribution) works as expected in these three Kubernetes Versions when working altogether.

Automated tests

Every module/distribution tests run on top of a kind cluster. This guarantees that the tests are run on a pristine cluster created just it time for the test and are reproducible. Also we get to test against several Kubernetes versions in parallel.

Take a look at the Quick Start page to create a Kubernetes Cluster using kind following by the distribution installation.

Fury Version/Kubernetes Version v1.14.Z v1.15.Z v1.16.Z
v1.0.0

Verified environments

SIGHUP has deployed this distribution across a wide variety of environments. Both unmanaged and managed environments.

Unmanaged

It does not matter if the Kubernetes nodes were created from a virtualized provider (AWS EC2, VMware vSphere…) or from plain instances (bare-metal). With a plain Kubernetes Cluster installed on these instances, SIGHUP can deploy the distribution on top of it.

Unmanaged Provider/Fury Version v1.0.0
AWS EC2
Oracle Cloud instances
VMware vSphere
hostingsolutions.it (vps)
arubacloud.com (vps)
bare-metal (dell, hp…)

Managed

If you choose to deploy Kubernetes in a Kubernetes Managed Service, SIGHUP can deploy the distribution on top of it.

Managed Provider/Fury Version v1.0.0
Google Kubernetes Engine 1.14
Google Kubernetes Engine 1.15
Azure Kubernetes Service 1.14

If you are in this scenario, some tweaks have to be done.

For example, SIGHUP includes a pre-preconfigured CNI plugin based on Calico but most Kubernetes Managed Services deploys its own CNI plugin. So, you have to disable the CNI deployment of this Kubernetes distribution otherwise you can encounter unexpected networking issues.

In addition to the CNI modification, there are other configurations that have to be applied/modified. Read carefully every module's documentation for more detailed information.



Last modified 25.06.2020: Updating module references (82f9ca7)