Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.
Awesome Lists | Featured Topics | Projects
https://github.com/sighupio/fury-distribution

Kubernetes Fury Distribution (Core Modules) - A battle-tested open-source Kubernetes distribution
https://github.com/sighupio/fury-distribution
cncf fury fury-distribution kubernetes kubernetes-distribution sighup
Last synced: about 12 hours ago
JSON representation
Kubernetes Fury Distribution (Core Modules) - A battle-tested open-source Kubernetes distribution
Host: GitHub
URL: https://github.com/sighupio/fury-distribution
Owner: sighupio
License: bsd-3-clause
Created: 2020-01-23T16:23:02.000Z (almost 5 years ago)
Default Branch: main
Last Pushed: 2024-10-29T08:20:31.000Z (2 months ago)
Last Synced: 2024-10-29T09:41:20.667Z (2 months ago)
Topics: cncf, fury, fury-distribution, kubernetes, kubernetes-distribution, sighup
Language: Smarty
Homepage: https://kubernetesfury.com/
Size: 4.94 MB
Stars: 162
Watchers: 16
Forks: 13
Open Issues: 9
Metadata Files:
- Readme: README.md
- Contributing: docs/CONTRIBUTING.md
- License: LICENSE
- Roadmap: ROADMAP.md
Awesome Lists containing this project

README

        


  


  Kubernetes Fury Distribution



Kubernetes Fury Distribution (KFD) is a certified battle-tested Kubernetes distribution based purely on upstream Kubernetes.


[![Build Status](http://ci.sighup.io/api/badges/sighupio/fury-distribution/status.svg?ref=refs/tags/v1.31.0)](http://ci.sighup.io/sighupio/fury-distribution)

[![Release](https://img.shields.io/badge/release-v1.31.0-blue?label=FuryDistributionRelease)](https://github.com/sighupio/fury-distribution/releases/latest)

[![Slack](https://img.shields.io/badge/slack-@kubernetes/fury-yellow.svg?logo=slack)](https://kubernetes.slack.com/archives/C0154HYTAQH)

[![License](https://img.shields.io/github/license/sighupio/fury-distribution)](https://github.com/sighupio/fury-distribution/blob/main/LICENSE)

## Overview

Kubernetes Fury Distribution (KFD) is a [CNCF certified](https://landscape.cncf.io/?selected=fury-distribution) battle-tested Kubernetes distribution based purely on upstream Kubernetes.

It is developed and maintained by [SIGHUP][sighup-site] and the community, and it is fully open source.

> 🎯 The goal of Fury is to turn any standard Kubernetes cluster into a fully-configured production-grade cluster.

## Un-distribution model 🧬

KFD uses an **un-distribution model**. This means that we:

- Rely only on open source solutions.

- Are free from vendor lock-in.

- Stay close to upstream Kubernetes and the cloud native landscape.

- Choose, configure and integrate a set of battle-tested open source tools.

## Architecture 🏗



  



Kubernetes Fury Distribution is structured on modules, and each module has a set of packages.

- A package is a single unit of functionality.

- A module groups packages that are functionally related together.

> All modules are open source, widely used, easily customizable, and pre-configured with sane defaults and tested to work well together.

The standard way to deploy KFD is to:

- Deploy all the [Core Modules](#core-modules-) of the distribution using [furyctl][furyctl].

- Deploy (if needed) any of the [Addon modules](#add-on-modules-) using [furyctl plugin][furyctl-plugins] feature.

See the getting started section below for more information.

### Recommended Hardware Requirements

KFD is a modular and composable system, so hardware requirements ultimately depend on the modules and configuration chosen. Having said that, for a production-grade cluster a good starting point would be:

A KFD production grade cluster will be composed of 3 node pools:

- Control Plane: 3 nodes in HA.

- Infrastructure: 3 nodes dedicated to running the infrastructural components of KFD (monitoring, logging, policy enforcement, etc., i.e. the modules).

- Workers: where the application workload will run. This is up to you.

- Load Balancers (optional): for on-premises installations, 2 load balancers in HA can be deployed to forward traffic to the control plane and the ingress controllers running in the infrastructure nodes.

#### Nodes sizing

| Node Role      | CPU (cores) | RAM (GB) | Disk (GB) | Qty. |

| -------------- | ----------- | -------- | --------- | ---- |

| Control Plane  | 2           | 8        | 50        | 3    |

| Infrastructure | 4           | 16       | 50        | 3    |

| Load Balancer  | 2           | 2        | 50        | 2    |

#### Storage

Some modules rely on persistent storage via PersistentVolumeClaims, by default (but configurable) the following capacity will be used:

| Description                                | Size (GB) |

| ------------------------------------------ | --------: |

| Prometheus (metrics storage)               |       150 |

| MinIO Monitoring (metrics storage, 20GBx6) |       120 |

| MinIO Logging (logs storage, 20GBx6)       |       120 |

| OpenSearch (logs storage)                  |        30 |

| MinIO Tracing (traces storage)             |       120 |

| **Total**                                  |   **540** |

### Core Modules 📦

Core modules provide essential functionality to the distribution for production-grade clusters.

| Module                          | Included Release               | Description                                                                                          |

| ------------------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------- |

| [Networking][networking-module] | ![Version][networking-version] | Networking functionality via Calico or Cilium CNIs                                                   |

| [Ingress][ingress-module]       | ![Version][ingress-version]    | Fast and reliable Ingress Controller and TLS certificate management                                  |

| [Logging][logging-module]       | ![Version][logging-version]    | A centralized logging solution based on the LoggingOperator + OpenSearch or Loki stacks              |

| [Monitoring][monitoring-module] | ![Version][monitoring-version] | Monitoring and alerting functionality based on Prometheus, AlertManager and Grafana                  |

| [Tracing][tracing-module]       | ![Version][tracing-version]    | Tracing functionality based on Tempo                                                                 |

| [Disaster Recovery][dr-module]  | ![Version][dr-version]         | Backup and disaster recovery solution using Velero                                                   |

| [OPA][opa-module]               | ![Version][opa-version]        | Policy and Governance for your cluster using OPA Gatekeeper and Gatekeeper Policy Manager or Kyverno |

| [Auth][auth-module]             | ![Version][auth-version]       | Improved auth for your Kubernetes Cluster and its applications                                       |

### Add-on Modules 📦

Add-on modules provide additional functionality to the distribution. Their release cycle is independent of KFD's.

| Module                              | Description                                                                  |

| ----------------------------------- | ---------------------------------------------------------------------------- |

| [Kong][kong-module]                 | Add Kong API Gateway for Kubernetes applications via Kong Ingress Controller |

| [Service Mesh][service-mesh-module] | Deploy a service mesh on top of KFD                                          |

| [Registry][registry-module]         | Integrate a Container Registry solution                                      |

| [Storage][storage-module]           | Rook (Ceph Operator) based Storage solution on Kubernetes                    |

| [Kafka][kafka-module]               | Apache Kafka event streaming for your Cluster                                |

## Get started with KFD 🚀

To get started with KFD, please head to the [quickstart guides on the documentation site](https://docs.kubernetesfury.com/docs/distribution/#%EF%B8%8F-how-do-i-get-started).

## Issues 🐛

In case you experience any issues feel free to [open a new issue](https://github.com/sighupio/fury-distribution/issues/new/choose).

If the problem is related to a specific module, open the issue in the module repository.

## Commercial Support 🛟

If you are looking to run KFD in production and would like to learn more, SIGHUP (the company behind the Fury ecosystem) can help. Feel free to [email us](mailto:[email protected]) or check out [our website](https://sighup.io).

## Support & Compatibility 🪢

Current supported versions of KFD are:

|                                  KFD Version                                   | Kubernetes Version |

| :----------------------------------------------------------------------------: | :----------------: |

| [`1.31.0`](https://github.com/sighupio/fury-distribution/releases/tag/v1.31.0) |      `1.31.x`      |

| [`1.30.0`](https://github.com/sighupio/fury-distribution/releases/tag/v1.30.0) |      `1.30.x`      |

| [`1.29.5`](https://github.com/sighupio/fury-distribution/releases/tag/v1.29.5) |      `1.29.x`      |

| [`1.28.5`](https://github.com/sighupio/fury-distribution/releases/tag/v1.28.5) |      `1.28.x`      |

> [!NOTE]

> Usually, KFD supports 3 versions simultaneously that compatible with 3 different underlying Kubernetes versions. With KFD v1.31.0 the support for KFD v1.28.x will be extended for some time, effectively providing support for 4 versions (1.28, 1.29, 1.30 and 1.31).

> See the [versioning](docs/VERSIONING.md) document for more details on KFD's version skew policy.

Check the [compatibility matrix][compatibility-matrix] for additional information about previous releases of the Distribution and the compatibility with `furyctl`.

Also, check the [versioning documentation file][versioning] to know more about the versioning scheme of the distribution and the upgrade path.

## CNCF Certified 🎓

Each version of the Kubernetes Fury Distribution that introduces compatibility with a new version of Kubernetes goes through a [conformance certification process with the CNCF][cncf-conformance]. Certified solutions are validated to ensure a set of guarantees such as consistency, timely updates and confirmability.

KFD has been certified by the [CNCF] (Cloud Native Computing Foundation) as a _Certified Kubernetes Distribution_ for all Kubernetes versions since [Kubernetes 1.12](https://github.com/cncf/k8s-conformance/pull/619). Clicking on the badge below you can see the certification process for the latest version of KFD:



    

        

    



## Roadmap

Find the updated roadmap in the [ROADMAP.md](ROADMAP.md) file.

## Contributing 🤝

If you wish to contribute please read the [Contributing Guidelines](docs/CONTRIBUTING.md).

## License

KFD is open-source software and it's released under the following [LICENSE](LICENSE)

[networking-module]: https://github.com/sighupio/fury-kubernetes-networking

[ingress-module]: https://github.com/sighupio/fury-kubernetes-ingress

[logging-module]: https://github.com/sighupio/fury-kubernetes-logging

[monitoring-module]: https://github.com/sighupio/fury-kubernetes-monitoring

[tracing-module]: https://github.com/sighupio/fury-kubernetes-tracing

[dr-module]: https://github.com/sighupio/fury-kubernetes-dr

[opa-module]: https://github.com/sighupio/fury-kubernetes-opa

[auth-module]: https://github.com/sighupio/fury-kubernetes-auth

[networking-version]: https://img.shields.io/badge/release-v2.0.0-blue

[ingress-version]: https://img.shields.io/badge/release-v3.0.1-blue

[logging-version]: https://img.shields.io/badge/release-v4.0.0-blue

[monitoring-version]: https://img.shields.io/badge/release-v3.3.0-blue

[tracing-version]: https://img.shields.io/badge/release-v1.1.0-blue

[dr-version]: https://img.shields.io/badge/release-v3.0.0-blue

[opa-version]: https://img.shields.io/badge/release-v1.13.0-blue

[auth-version]: https://img.shields.io/badge/release-v0.4.0-blue

[kong-module]: https://github.com/sighupio/fury-kubernetes-kong

[service-mesh-module]: https://github.com/sighupio/fury-kubernetes-service-mesh

[registry-module]: https://github.com/sighupio/fury-kubernetes-registry

[storage-module]: https://github.com/sighupio/fury-kubernetes-storage

[kafka-module]: https://github.com/sighupio/fury-kubernetes-kafka

[kong-version]: https://img.shields.io/github/v/release/sighupio/fury-kubernetes-kong

[service-mesh-version]: https://img.shields.io/github/v/release/sighupio/fury-kubernetes-service-mesh

[registry-version]: https://img.shields.io/github/v/release/sighupio/fury-kubernetes-registry

[storage-version]: https://img.shields.io/github/v/release/sighupio/fury-kubernetes-storage

[kafka-version]: https://img.shields.io/github/v/release/sighupio/fury-kubernetes-kafka

[compatibility-matrix]: https://github.com/sighupio/fury-distribution/blob/main/docs/COMPATIBILITY_MATRIX.md

[versioning]: https://github.com/sighupio/fury-distribution/blob/main/docs/VERSIONING.md

[furyctl]: https://github.com/sighupio/furyctl

[furyctl-plugins]: https://github.com/sighupio/furyctl?tab=readme-ov-file#plugins

[sighup-site]: https://sighup.io

[CNCF]: https://landscape.cncf.io/?group=certified-partners-and-providers&item=platform--certified-kubernetes-distribution--fury-distribution

[cncf-conformance]: https://www.cncf.io/certification/software-conformance/