Dependence on Microsoft 365 and Teams has never been greater, and the pressure is on for IT teams to deliver exceptional user experiences – anytime, anywhere. The modern workplace sees users connecting from the office, home, and pretty much any place in between. This hybrid work model has a significant impact on IT, the network and the overall quality of service perceived by the users.
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.
We all remember when Facebook, WhatsApp, and Instagram shut down in April of last year for a whole day. And while it was terrible for their company—it’s an educational moment for the rest of us to learn from. Facebook’s status page is self-hosted, and that puts their status pages at risk of the exact issue it’s designed to tell you about.
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.
