Skip to main content
Version: 1.26.6


While designing and developing KFD, we follow the following principles:

🧬 Un-distribution model

KFD follows the un-distribution model. This concept originates with Heptio. In simple words, the idea behind this model is to avoid creating vendor lock-in by relying and integrating only on open source technologies without custom modifications.

This freedom from vendor lock-in allows the flexibility to deploy KFD in various environments and migrate off KFD to another Kubernetes distribution if you decide to.

In a nutshell, what KFD does is stay close to upstream Kubernetes and the cloud-native landscape to provide you with a set of pre-configured battle-tested open-source tools.

📦 Modularity

KFD has modularity as its design principle. The distribution does not have strict requirements or strong interdependencies between modules.

You can pick and choose only the one you need.

📖 Openness

All of KFD is fully open source. The distribution itself, its modules and, all the support tools that we develop.

You can find the visit SIGHUP's GitHub repositories to check out the source code here.

🚀 Only upstream Kubernetes

We don't want to diverge from upstream Kubernetes and re-invent the wheel. We 💙 Kubernetes as it is.

🌱 Substrate independence

You can deploy KFD on top of any cluster or even from scratch, both on-premises and all major cloud providers.

There are various installers that integrate best practices to deploy a KFD cluster in multiple environments.

🤖 Automations

Using our furyctl CLI tool it is possible to provision a complete cluster from scratch, automating the usage of installers and modules.