Sometimes things go wrong. This guide is aimed at making them right. It has two sections:
You should also check the known issues for the release you’re using.
If your problem isn’t answered by any of the guides above, there are variety of ways for you to get help from the Kubernetes team.
The documentation on this site has been structured to provide answers to a wide
range of questions. Concepts explain the Kubernetes
architecture and how each component works, while Setup provides
practical instructions for getting started. Tasks show how to
accomplish commonly used tasks, and Tutorials are more
comprehensive walkthroughs of real-world, industry-specific, or end-to-end
development scenarios. The Reference section provides
detailed documentation on the Kubernetes API
and command-line interfaces (CLIs), such as
You may also find the Stack Overflow topics relevant:
Someone else from the community may have already asked a similar question or may be able to help with your problem. The Kubernetes team will also monitor posts tagged Kubernetes. If there aren’t any existing questions that help, please ask a new one!
The Kubernetes team hangs out on Slack in the
#kubernetes-users channel. You
can participate in discussion with the Kubernetes team here.
Slack requires registration, but the Kubernetes team is open invitation to
anyone to register here. Feel free to come and ask
any and all questions.
Once registered, browse the growing list of channels for various subjects of
interest. For example, people new to Kubernetes may also want to join the
#kubernetes-novice channel. As another example, developers should join the
There are also many country specific/local language channels. Feel free to join these channels for localized support and info:
The Kubernetes / Google Container Engine mailing list is firstname.lastname@example.org
If you have what looks like a bug, or you would like to make a feature request, please use the Github issue tracking system.
Before you file an issue, please search existing issues to see if your issue is already covered.
If filing a bug, please include detailed information about how to reproduce the problem, such as: