Operations | Monitoring | ITSM | DevOps | Cloud

From containerized workloads to microservice architectures, developers are rapidly adopting new technology that allows organizations to scale their products at unprecedented rates. In order to make sense of these complex deployments, many teams are abstracting applications away from the environments in which they run. Because of this trade-off, developers and security teams lose the access to the unified context from infrastructure to application needed to fully secure their services.

Kubernetes and robotics make a great match. However, as we have seen, robots running ROS 2 can be tricky to set up on Kubernetes. This blog series has explored running ROS 2 on Kubernetes, set up a simple talker and listener, and distributed that demo across three machines. The configurations presented may not quite fit your implementation, and you may want to dig a bit deeper into network traffic when troubleshooting.

Alert Response as Code is Interlink’s software-based, programmatic model for identifying incident alerts and driving an automated response. IT teams can automate the triggering of recovery processes that would otherwise involve running individual, manual steps across multiple applications, devices and operating systems.

re:Invent 2020 is here and while you don't have to find Galileo 601 or Hall G it can still be a lot to manage. Our team combed through the massive re:Invent schedule to bring you the the most important sessions related to serverless, architecture, and DevOps. In addition to the Serverless Track and the Keynotes we recommend these particular sessions. If you need help putting your schedule together we love Cloud Pegboard!

I recently found out Travis CI is ending its free-for-opensource offering, and looked at the alternatives. I recently got badly burned by giving an external CI service access to my repositories, so I am now wary of giving any service any access to important accounts. Github Actions, being a part of Github, therefore looked attractive to me. I had no experience with Github Actions going in. I have now spent maybe 4 hours total tinkering with it.