Should you use small or large instances in a Kubernetes cluster? It depends. You should consider a few factors when selecting an instance type:

• What kind of workloads you deploy (i.e. memory and CPU requirements).
• The blast radius you can tolerate.
• How you design your HA strategy.
• How many resources are available to the pods.

This calculator helps you select what’s right from over 700 instances from the major cloud providers.

This article compares six static tools to validate and score Kubernetes YAML files for best practices and compliance.

One of the challenges with YAML is that it’s rather hard to express constraints or relationships between manifest files.

What if you wish to check that all images deployed into the cluster are pulled from a trusted registry?

How can you prevent Deployments that don’t have PodDisruptionBudgets from being submitted to the cluster?

When it comes to configuring Kubernetes…

You should use tools such as yq and kustomize to template YAML resources instead of relying on tools that interpolate strings such as Helm.

How do you know if your Kubernetes cluster is production-ready?

If you’re a beginner, it’s hard to tell what you’re missing. The subject is soo vast and it’s easy to lose sight on what’s the right path to production.

And even if you’re an expert, remembering all networking, storage, cluster, and application development best practices is impossible. There are so many.

Here is a curated a list of best practices for Kubernetes that helps you drive your roadmap to production.

Check things off the list and keep track as you go. ✅

You should have a plan to roll back releases that aren’t fit for production. In Kubernetes, rolling updates are the default strategy to release software.

In a nutshell, you deploy a newer version of your app and Kubernetes makes sure that the rollout happens without disrupting the live traffic. However, even if you use techniques such as Rolling updates, there’s still risk that your application doesn’t work the way you expect it at the end of the deployment.

Kubernetes has a built-in mechanism for rollbacks. Learn how it works in this article.

Have you ever created a Kubernetes cluster and wondered what type of worker nodes you should use? For example, if you’re on AWS, should you use many small and cheap t2.micro instances, or some few powerful m5.xlarge instances?

This article discusses the pros and cons of using different worker node sizes in your cluster.

Have you ever stared at the terminal window but don’t remember which Kubernetes cluster it is set up for? Are you bored of typing kubectl get pods for the millionth time? Learn how to boost your kubectl productivity with these 6 tips

A fascinating read, answering this question:

What if you were to leverage a tool designed to run in data centres such as Kubernetes to run a solar plant?

Spot Instances are a great way to cut costs on your cloud bill, but you should embrace the volatility and accept that they might go away at any moment. How can you deal with unreliable infrastructure?

In this highly visual and scroll friendly post from Daniele, you’ll follow the evolution of monolith, to components, to VMs, to today’s world of Kubernetes and cloud. Daniele writes:

Kubernetes and Docker? What is the difference? Is it just a fad or are those two technologies here to stay? If you heard about the Docker and Kubernetes, but you aren’t sold on the idea and don’t see the point in migrating, this article is for you. 
Learn how you can leverage Kubernetes to reduce infrastructure costs and accelerate your software delivery.