The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Hey, Matt from GitKraken here. I’ll admit, we’re a tad obsessed with developer productivity. Tools like GitKraken Client and GitLens are great for helping any developer go further, faster. But building software is most often a team sport. So over the past year, customers of all sizes have been imploring us to fill two important voids.
This second last part of the “Implementing Backstage” series explains how to use the Kubernetes plugin in Backstage using real-world scenarios. The previous installments covered getting started, using the core features, integrating with existing tools using plugins, and security and compliance. If you’re entirely new to Backstage and want to learn more, you can read the first entry in the “Evaluating Backstage” series.
This final part of the “Implementing Backstage” series focuses on how to deploy Backstage on Kubernetes. This tutorial is a direct continuation of Using the Kubernetes Plugin in Backstage, which you should complete before tackling this one. The other installments in this series covered getting started, using the core features, integrating with existing tools using plugins, and security and compliance.
Kubernetes integrations are now available for AutoSys, dSeries, and Automic Automation. It wasn’t that long ago that teams in many organizations started dipping their toes into the world of containers and microservices. It didn’t take long for this approach to application development and orchestration to take hold, and for Kubernetes to emerge as a dominant, broadly used technology.
As software engineers, we all know that troubleshooting often involves sifting through heaps of data points — scanning metrics, reading logs, checking resource status and analyzing events. We manually connect the dots, and if we're experienced enough, we might spot an issue that's about to become a problem. At StackState, we've faced these same challenges.
