Operations | Monitoring | ITSM | DevOps | Cloud

Things are changing. Technology differences between serverless and container-based systems are rapidly blurring. In 2020, Amazon Web Services (AWS) enabled AWS Lambda to package and deploy functions as container images instead of bundling all of a function’s code and dependencies in a.zip file. Today, more organizations are increasingly deploying Lambda functions as Docker container images. These companies want to reap the benefits of serverless computing, containers, and container orchestration.

The customer is the lifeblood of any company, and a good customer has the potential to make a huge impact on the direction and success of your business. Here at Cycle.io, we are no exception. We believe that when you come to Cycle, you are not only getting great tech but also receiving an excellent customer experience. The customers we work with every day are paramount in driving innovation and keeping us honest.

Have you ever needed to serve multiple customers with a single instance of your application but ran into challenges like isolating each customer's data and configuration? If you have, then you've encountered a multi-tenant architecture. In this blog post, we'll introduce the core concepts behind multi-tenancy and explore how it works. We'll then dive into how Kubernetes, the popular container orchestration platform, provides primitives that enable building multi-tenant architectures.

Monitoring and observability have become the backbone of reliable software systems. OpenTelemetry, a CNCF project, has gained immense traction as the go-to framework for collecting and exporting telemetry data. But what makes it even more powerful is its Collector—a vendor-agnostic tool that simplifies data processing. Combine that with Docker, and you’ve got a robust, portable, and scalable observability solution.

In modern application development, changes happen constantly: Deployments are pushed, feature flags are toggled, and Kubernetes events reshape infrastructure, to name just a few. While these practices drive innovation and scalability, they also introduce complexity—especially during incidents. Fragmented tools and workflows across teams and organizations make it difficult to pinpoint the root causes of issues, leading to longer resolution times.

The Kubernetes Monitoring Helm chart 2.0 is here, and it comes with some exciting changes to improve your experience collecting observability data. The Kubernetes Monitoring Helm chart makes it easy to start gathering telemetry data from your Kubernetes clusters. With one deployment, you can capture all of the metrics, logs, traces, and profiles from your cluster and the applications running on it!

Managing DNS records in Kubernetes at scale is complex, especially as clusters grow and the number of applications increases. Enter ExternalDNS—a tool designed to automate DNS record synchronization with Kubernetes resources, providing the agility and scalability needed for modern application environments.

Managing observability in cloud-native environments can feel like juggling a thousand things at once. OpenTelemetry makes this easier by becoming a favorite among developers for collecting, processing, and exporting telemetry data without breaking a sweat. Now, let’s talk about the OpenTelemetry Helm Chart. It’s like having a shortcut button for deploying OpenTelemetry in Kubernetes.

In formal terms, OpenTelemetry is an open source framework used for instrumenting, generating, collecting, and exporting telemetry data for applications, services, and infrastructure. It provides vendor-neutral tools, SDKs and APIs for generating, collecting, and exporting telemetry data such as traces, metrics, and logs to any observability backend, including both open source and commercial tools.