Over the past six months, I have come to believe that talking about Signals in the context of Observability is a mistake. To properly support distributed systems, we need to change how we observe them - the "Signal Braid" is no longer enough.
Today we're setting up a Kubernetes Logging Solution using Loggly and some simple Kubernetes commands.
Here we have a simple solution that can be used to inject secrets into your Kubernetes Clusters with minimal effort, when you do not have strict security requirements for your workloads.
Time to secure our cluster to ensure our traffic can't be snooped on by any baddies. In part 3, we use JetStack's `cert-manager` to automatically provision certificates and secure communication between the user and our `nginx-ingress` pods.
Let's get up and running using `nginx-ingress` on our Kubernetes cluster.
I just went through the process of setting up my Kubernetes Cluster, and it was pretty easy the third time around! So, I thought I'd put up a series of tutorials that focus on getting a Kubernetes Cluster up and running with Ingress, Certificates, and a basic Service.
"Chaos Engineering" means introducing intentional errors into your environment to test its operational resilience. Here's a story about chaos and small steps you can take as part of your DevOps development process to begin your journey to developing more resilient applications.