Deckhouse is an Open Source project, and we enthusiastically encourage anyone that has the desire to contribute to it on GitHub.
To ensure that Deckhouse’s development remains vigorous and sustainable, we’ve offered the platform in two editions:
Community
Enterprise Edition (EE)
A commercial version that boasts a breadth of additional features along with various subscription options. Its code is open as well, but it’s not free, nor is the license Open Source.
Community Edition (CE)
An Open Source version free of charge, which features the key Deckhouse functions. Its code can be accessed under the Apache 2.0 license.
Technical core
Deckhouse Platform follows the upstream version of Kubernetes, using that as a basis to build all of its features and configurations on.
Deckhouse Platform’s basic functions are implemented via two building blocks: shell-operator & addon-operator. Both have been available as Open Source projects since April/May 2019.
Aside from Deckhouse, various vendors (including KubeSphere, Confluent, and Adobe, just to name a few) and DevOps/Kubernetes enthusiasts have adopted these tools to implement instruments of their own.
To sum it up in a nutshell, Deckhouse Platform — as a Kubernetes distribution — is an upstream Kubernetes packed with a whole bunch of modules based on addon-operator.
Shell-operator
A tool used to create Kubernetes operators (any logic to be executed when some event is triggered in K8s).
Addon-operator
A system for managing Kubernetes modules based on shell-operator in a consistent, automated manner.
Online community
Use GitHub Issues & Discussions to ask your questions, report bugs, and share your experience.
Follow Deckhouse on Twitter to stay informed about everything that’s going on.
Participate in chat in the project’s Telegram channel: @deckhouse.
Read and dive into the nuts and bolts of Deckhouse in our tech blog.
How to contribute
Your contributions are always greatly appreciated! To learn how you can contribute to the Deckhouse code base please visit this page.
