Operations | Monitoring | ITSM | DevOps | Cloud

Companies face multiple challenges when migrating their applications and services to the cloud, and one of them is infrastructure management. The ideal scenario would be that all workloads could be containerized. In that case, the organization could use a Kubernetes-based service, like Amazon Web Services (AWS), Google Cloud or Azure, to deploy and manage applications, services and storage in a cloud native environment. Unfortunately, this scenario isn’t always possible.

As the movement to the cloud has grown, so has the use of containers as an effective way to package, distribute, and deploy applications. As surveys show, Kubernetes is the most widely used orchestration engine for managing cloud-native containers. Kubernetes automates deployment, auto-scaling, resource optimization, backup and recovery, and enables containers to run across different environments, eliminating the need to develop separate versions for each operating environment.

This blog will cover what the Calico/VPP dataplane is and demonstrate the performance and flexibility advantages of using the VPP dataplane through a benchmarking setup. By the end of this blog post, you will have a clear understanding of how Calico/VPP dataplane, with the help of DPDK and accelerated memif interfaces, can provide high throughput and low-latency Kubernetes cluster networking for your environment.

Sysdig Monitor has long integrated with a variety of Notification Channels, allowing users to forward alerts to a multitude of third-party services. Currently, users can choose to forward Sysdig Monitor’s alerting events to external services like PagerDuty, Slack, Email, Microsoft Teams, and many more.

While more and more teams are adopting Kubernetes as their standard container orchestration technology, cost insight is lacking. Teams often don’t know how much they’re spending, where in their organization they are spending, or what is driving their infrastructure cost increases. OpenCost helps alleviate this problem by bringing real-time cost monitoring to Kubernetes workloads with a solution that encompasses both an open specification and an open source project.

Our latest open-source project, Helm-Dashboard, just crossed 3K stars on GitHub (and hundreds of daily active users), only three months since it was released! We thought this milestone was a good chance to take a look back at our journey, announce the release of v. 1.0.0, discuss future plans, and, most importantly, give our utmost thanks to the amazing contributors and Kommunity members that made it all possible! What capabilities would you like to see next in Helm-Dashbaord?

Creating effective Continuous Integration pipelines is a daunting task that requires combining knowledge from different areas. At Codefresh we have always strived for a fast feedback loop between both customers and prospects in regards to pipeline speed and simplicity. We always want to improve the onboarding process for everybody regardless of their position in the cloud native journey.

In a market downturn, reducing spending would seem to be the prudent course to pursue. However, surveys show that most companies intend to increase IT spending in 2023. A Spiceworks Ziff Davis survey, for example, found that even for businesses that plan to cut back in other areas, tech spending will increase. The survey found that more than one-half of companies surveyed planned to increase IT spending (compared with only 6% planning to decrease spending).