Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes is currently the de-facto container orchestration system on the market. Both small and large companies adopt it, and all major cloud providers offer it as a service. However, Kubernetes is a complex and layered platform, so you can’t just jump into it. There are three essential stages for each application: design, deployment, and operation. This blog post will focus on operation, where you need to monitor and troubleshoot your deployed applications.

Welcome to the concluding chapter of this journey on embedded Linux development with Ubuntu. We covered a lot of ground, so let us quickly recap what we learned so far. In Part I we introduced Snaps, software packages designed for the world of IoT. Snap packages isolate and encapsulate an entire application, increasing the security and stability of embedded devices. Snapcraft is the command-line tool to build snaps.

Multi cloud has long been a contentious topic when you talk about cloud infrastructure. Infrastructure as code tools such as Terraform and Pulumi have made deploying to any cloud much easier - you can now use a single interface to deploy infrastructure to virtually any cloud environment. However, the effort of creating infrastructure for each cloud provider still requires significant expertise and time to get right, leading many to see it as a effort not worth taking.

Kubernetes is today’s leading container management platform, due to its comprehensive API and developer-friendly features. Using Kubernetes, you can create scalable and reliable applications that run on-premises systems and public clouds. Its out-of-the-box features allow it to distribute hundreds of instances over data centers and keep them up and running. In order to catch up with the automation level of Kubernetes, developing and deploying applications requires more autonomy.