Monitoring, Logging, and Debugging
Sometimes things go wrong. This guide is aimed at making them right. It has two sections:
- Debugging your application - Useful for users who are deploying code into Kubernetes and wondering why it is not working.
- Debugging your cluster - Useful for cluster administrators and people whose Kubernetes cluster is unhappy.
You should also check the known issues for the release you're using.
Getting help
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 community.
Questions
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 kubectl.
Help! My question isn't covered! I need help now!
Stack Exchange, Stack Overflow, or Server Fault
If you have questions related to software development for your containerized app, you can ask those on Stack Overflow.
If you have Kubernetes questions related to cluster management or configuration, you can ask those on Server Fault.
There are also several more specific Stack Exchange network sites which might be the right place to ask Kubernetes questions in areas such as DevOps, Software Engineering, or InfoSec.
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 ensure that your question is on-topic on Stack Overflow, Server Fault, or the Stack Exchange Network site you're asking on, and read through the guidance on how to ask a new question, before asking a new one!
Slack
Many people from the Kubernetes community hang out on Kubernetes Slack in the #kubernetes-users channel.
Slack requires registration; you can request an invitation,
and registration is open to everyone). Feel free to come and ask any and all questions.
Once registered, access the Kubernetes organisation in Slack
via your web browser or via Slack's own dedicated app.
Once you are 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
#kubernetes-contributors channel.
There are also many country specific / local language channels. Feel free to join these channels for localized support and info:
| Country | Channels |
|---|---|
| China | #cn-users, #cn-events |
| Finland | #fi-users |
| France | #fr-users, #fr-events |
| Germany | #de-users, #de-events |
| India | #in-users, #in-events |
| Italy | #it-users, #it-events |
| Japan | #jp-users, #jp-events |
| Korea | #kr-users |
| Netherlands | #nl-users |
| Norway | #norw-users |
| Poland | #pl-users |
| Russia | #ru-users |
| Spain | #es-users |
| Sweden | #se-users |
| Turkey | #tr-users, #tr-events |
Forum
You're welcome to join the official Kubernetes Forum: discuss.kubernetes.io.
Bugs and feature requests
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:
- Kubernetes version:
kubectl version - Cloud provider, OS distro, network configuration, and container runtime version
- Steps to reproduce the problem