Operations | Monitoring | ITSM | DevOps | Cloud

Creating a DevOps workflow to optimize application deployments to your Kubernetes cluster can be a complex journey. I recently demonstrated how to optimize your local K8s development workflow with Rancher Desktop and Skaffold. If you haven’t seen it yet, you can watch it by viewing the video below. You might be wondering, “What happens next?” How do you extend this solution beyond a local setup to a real-world pipeline with a remote cluster?

Every technical team in the software industry is familiar with technical debt. That is because every software team incurs technical debt along the way. This article answers some critical questions about technical debt. It reviews what technical debt is and what its causes are, why it is essential to address technical debt, and how this debt accumulates.

This article was inspired by our recent "5 tools to increase Kubernetes developer productivity" video, hosted by Saiyam Pathak and Kunal Kushwaha. Over the years Kubernetes has become the de facto orchestration platform, as such it's crucial that developers have the right set of tools to increase their productivity for development and operations. In this article, we take a look at five such tools that can help developers inprove productivity while when Kubernetes. Let’s jump in.

Continuing on from Part One where we went through a brief history of containers and Kubernetes then Dockerized a NodeJS application, now we are ready to deploy to Kubernetes. If this is your first or nth time deploying to Kubernetes, Shipa makes this simple. You don’t have to worry about authoring multiple Kubernetes manifests and templates to deploy your application, all you need is an image.

Live kernel patching is an essential component of your Linux server management and vulnerability remediation strategy. Patching encompasses all installed software, and software essential for baseline operation of the OS. The most dynamic component of Linux, essential for baseline operation, is the kernel.

We are currently pushed to discover creative and unique means for information exchange, and fortunately, new technology enables us to do so. However, we occasionally have issues such as being unable to access desktop displays or gadgets crashing. Remote desktop access comes in handy for this.

Today, I was working on our Terraform Provider, and I noticed that I never tried to deploy an application from scratch on a new and clean AWS account. Meaning, an empty AWS account - with 0 resources created. No VPC, no EC2, no Load Balancer, nothing... just an IAM user to get access to my AWS account programmatically. This post explains what I did and how it took 37 minutes and 33 seconds to literally: 😅 Let's explain all of that!

Why this combination you ask? Load testing is my passion, and I am partial to Kubernetes. I challenged myself to share a use case that many could relate to, focused on a business critical application. Websites came to mind and WordPress is the world’s most popular website management system. Of course, nginx is the most popular web server so let’s throw that into the mix. And Kubernetes? With more than 50% of corporations adopting Kubernetes in 2021, what better system to run in.