This post was co-written by Kirti Apte and Gabry (Maria Gabriella) Brodi. Over the last couple of years, customers have been adopting Kubernetes and microservice-based application deployment models for various technology and business reasons. In fact, there is a trend that customers are now looking to the next set of use cases that include applications across multiple clouds, as well as edge clouds.

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.

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.

VMware Tanzu Kubernetes Grid has become a trusted tool to automate the lifecycle of Kubernetes clusters. The simplicity of management has quickly turned it into a valuable asset in many organizations. The release of Tanzu Kubernetes Grid 2.1 adds new features that enhance lifecycle management and extends Kubernetes to the edge.

The first thing to know when exploring APIs vs microservices is that there’s not a dichotomous relationship between these two technical approaches. Instead, you want to build an understanding of how these two technologies relate to each other—and they do, in a big way. So, organizations don’t need to embrace either an API-first or microservices-first strategy.

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?

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).

Kubernetes has firmly established itself as the leading choice for container orchestration thanks to its robust ecosystem and flexibility, allowing users to scale their workloads easily. However, the complexity of Kubernetes can make it challenging to set up and may pose a significant barrier for organizations looking to adopt cloud native technology and containers as part of their modernization efforts.