Submitting blog posts and case studies

    The Kubernetes blog is used by the project to communicate new features, community reports, and any news that might be relevant to the Kubernetes community. This includes end users and developers. Most of the blog’s content is about things happening in the core project, but we encourage you to submit about things happening elsewhere in the ecosystem too!

    Anyone can write a blog post and submit it for review.

    • Blog posts should not be vendor pitches.
      • Articles must contain content that applies broadly to the Kubernetes community. For example, a submission should focus on upstream Kubernetes as opposed to vendor-specific configurations. Check the Documentation style guide for what is typically allowed on Kubernetes properties.
      • Links should primarily be to the official Kubernetes documentation. When using external references, links should be diverse - For example a submission shouldn’t contain only links back to a single company’s blog.
      • Sometimes this is a delicate balance. The is there to give guidance on whether a post is appropriate for the Kubernetes blog, so don’t hesitate to reach out.
    • Blog posts are not published on specific dates.
      • Articles are reviewed by community volunteers. We’ll try our best to accommodate specific timing, but we make no guarantees.
      • Many core parts of the Kubernetes projects submit blog posts during release windows, delaying publication times. Consider submitting during a quieter period of the release cycle.
      • If you are looking for greater coordination on post release dates, coordinating with CNCF marketing is a more appropriate choice than submitting a blog post.
      • Sometimes reviews can get backed up. If you feel your review isn’t getting the attention it needs, you can reach out to the blog team via to ask in real time.
    • Blog posts should be original content
      • The official blog is not for repurposing existing content from a third party as new content.
      • The license for the blog allows commercial use of the content for commercial purposes, but not the other way around.
    • Blog posts should aim to be future proof
      • Given the development velocity of the project, we want evergreen content that won’t require updates to stay accurate for the reader.
      • It can be a better choice to add a tutorial or update official documentation than to write a high level overview as a blog post.
        • Consider concentrating the long technical content as a call to action of the blog post, and focus on the problem space or why readers should care.

    Technical Considerations for submitting a blog post

    Submissions need to be in Markdown format to be used by the Hugo generator for the blog. There are on how to use this technology stack.

    The SIG Docs blog subproject manages the review process for blog posts. For more information, see .

    To submit a blog post follow these directions:

    Submit a case study

    Case studies highlight how organizations are using Kubernetes to solve real-world problems. The Kubernetes marketing team and members of the collaborate with you on all case studies.

    Have a look at the source for the existing case studies.

    Refer to the and submit your request as outlined in the guidelines.