Glossary
This is a list of terms that will be commonly used throughout this documentation, along with their meanings.
Distribution
Bundle of components and default configurations that create a production-ready Kubernetes installation.
Installer
An installer is a Terraform module or a set of Ansible roles that can be used by a user to install a Kubernetes Cluster. It abstracts the differences that may exist across different kinds of providers to ensure a consistent deployment of KFD on all of them.
The list of available installers for KFD is available at the Installers page.
Module
A set of open-source packages grouped together to fulfill a specific need within the distribution. For example, Dex and Pomerium are both part of the Auth module.
You can see all included modules and their documentation in the Modules page.
Package
A package is a single unit of functionality. More specifically, it is an open-source project for which KFD provides a standard configuration.
One or more packages are grouped together in Modules (see above).
Modules and packages are loosely coupled. You don't have to deploy all the distribution modules, and you don't have to deploy all the packages inside a module. So it's up to you to decide which module could be helpful for your scenario and which tool you want to use or not.
Providers
They are the different Kinds available to be used in a furyctl.yaml file. They are JSON Schemas that represent the available parameters to be configured in a KFD cluster.
All schemas share a good amount of parameters, but some of them can be different depending on which Kind you are using. You can find the documentation for each Provider here
Provisioner
A set of Terraform and/or Ansible config files to initialize some of the needed resources before actually installing KFD.
Upgrade path
It's the standardized set of steps to be executed when upgrading from one KFD version to another. KFD defines several upgrade paths, sometimes they can also allow to jump versions. They can be different depending on the starting version and the kind of installer.
See furyctl get upgrade-paths --help for more info.