Operations | Monitoring | ITSM | DevOps | Cloud

Welcome to another iteration of What’s New in Sysdig in 2022! The “What’s new in Sysdig” blog has fallen to me, Jason Donahue, for the month of March! I am a Solutions Engineer based in New Jersey and a member of the Sysdig US East Enterprise team since September, 2021. I have worn many hats in my career, from Networking to Systems Administration to Software Engineer.

Kubernetes. Nowadays it seems companies in the industry are divided into two pools: those that already use it heavily for their production workloads and those that are migrating their workloads into it. The issue with Kubernetes is that it is not a single system the way Redis RabbitMQ or PostgreSQL are. It is a combination of several control plane components (for example etcd, api server) that run our workloads on the user (data) plane over a fleet of VMs.

The CNCF Annual Survey 2021 is in and makes for some very encouraging reading for the future of Kubernetes and its place in the tech landscape. The 2021 survey was the biggest yet, with some 3,829 developers, engineers, architects, and C-level execs in the cloud native space taking part. Here are some of our key takeaways…

When designing a solution, you should keep future needs in mind. If the number of users increases dramatically in a short period of time, the solution should be scalable enough to handle the new growth. Making systems scalable on cloud is relatively easier as compared to scaling on-premises infrastructure. AWS has provided excellent tools/services to enable your applications for as much scalability as you want.

Read a blow-by-blow analysis of two of the heavyweights in world of DevOps: when should you bet on Terraform, and what calls for Kubernetes?

Let’s face it. Gaining a competitive advantage in the target market is expensive. Even if you have a good idea and its execution plan in mind, operations related to management, storage, networking, service provisioning, security, and application management will cost you a fortune. To say the least, a cutting-edge IT infrastructure, a reliable team, and a strategy for rapid product releases or expansion/scaling is a must for your product’s success.

Creating development environments on Kubernetes has been a topic discussed many times. As teams increase the number of developers using Kubernetes, it continues to be a challenge for many developers. This post aims to show how you can leverage Shipa to create environments and make them available to developers in just a few minutes!

Cloud-native is an evolving architecture. Existing vendors will keep on evolving their offerings and different teams inside your organization should be able to use the tool that will support them better in delivering their desired outcome fast. By implementing a standard application layer, you enable teams to adopt what works best for them while the DevOps team can focus on adopting the infrastructure components they believe to be best to support their organization.