Monitoring, Logging, and Debugging

    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 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 community.

    Help! My question isn’t covered! I need help now!

    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 and that you read through the guidance on how to ask a new question, before !

    Many people from the Kubernetes community hang out on Kubernetes Slack in the channel. Slack requires registration; you can , 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 channel. As another example, developers should join the #kubernetes-dev channel.

    You’re welcome to join the official Kubernetes Forum: discuss.kubernetes.io.

    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.

    • Kubernetes version: kubectl version
    • Cloud provider, OS distro, network configuration, and container runtime version