Welcome to the Canonical Kubernetes community¶
This rapidly growing community is a diverse bunch of people - developers, Kubernetes admins, inventors, researchers, students… and we all share the joy of a reliable, flexible and secure version of upstream Kubernetes. The team recognizes the important role each and every user plays in the success of the project as a whole and how valuable your contributions are.
Do you have questions?¶
Do you have questions about Canonical Kubernetes? Perhaps you want to share some ideas on how to best achieve a certain goal or maybe some aspect of your Kubernetes doesn’t behave the way you expect. Perhaps you’d just like some advice from more experienced users. There are a number of ways to get in touch:
Using the Kubernetes slack: find us in the #canonical-kubernetes channel
On the Ubuntu Discourse
For more formal support, please see the support options available to you on the Ubuntu website.
Found a bug?¶
You can always track what is going on with development by watching our GitHub repository. This is also the best place to file a bug if you find one, or of course you are also welcome to contribute to the code.
Contributing to the code?¶
Canonical Kubernetes is proudly open source, published under the GPLv3 license.
We welcome contributions to the code. Please see the
repository CONTRIBUTING.md
file
for more information on contributing.
Contributing to docs?¶
Our documentation is extremely important to us and is actively maintained by the entire team. That doesn’t mean that it can’t be improved though. Every page in the documentation has an “Contribute to this page” link (pencil icon) which takes you to the GitHub editor to make small changes. For larger contributions, please see the docs contributing guide.
Code of conduct¶
Building a fair, open and inclusive community is important to us. We think adopting a code of conduct is a sensible way to make sure that everybody participating understands what the expectations and obligations are. The team adopts the Ubuntu Code of Conduct 2.0, and we use these as the guidelines for participation.