Is Strimzi production ready?

Is Strimzi production ready? Yes. Running Apache Kafka on Kubernetes has become increasingly common, and Strimzi is now part of many production Kafka environments.

When do team use Strimzi
Teams using Strimzi often point to the same advantages:

• Kubernetes-native operations
• GitOps-based management
• automation through Kubernetes tooling
• flexible deployment models
• easier scaling and configuration management

At the same time, production environments also introduce operational realities around:

• upgrades
• monitoring
• maintenance windows
• incident handling
• recovery planning

Experiences shared by engineering teams running Strimzi in production show a fairly consistent picture: Strimzi is widely seen as stable and capable at scale, but successful operations still depend on strong operational processes and maintenance practices.

This article looks at the operational patterns, challenges, and lessons commonly shared by teams running Strimzi in production Kafka environments.

Is Strimzi Kubernetes-Native?

What is the advantages of Strimzi is its alignment with Kubernetes operational models.

Teams commonly use:

• Kubernetes custom resources
• GitOps workflows
• Helm-based deployments
• ArgoCD or FluxCD automation
• declarative configuration management

Operational tasks often managed through Strimzi include:

• Kafka clusters
• topics
• users
• ACLs
• connectors

Several teams described Kafka operations becoming part of their broader Kubernetes automation strategy.

One production user summarized it directly:

“It’s the way you should use Kafka on k8s.”

Can Strimzi Scale kafka?

Yes: Engineering teams reported running Strimzi successfully across a variety of production scales.

Examples shared included:

• around 1 million messages per second across multiple clusters
• sustained 500k–1M events/sec
• thousands of Kafka topics
• large Kafka Connect deployments
• multi-region architectures
• multi-cloud environments
• mTLS-secured clusters
• AKS and EKS deployments

Some users also mentioned operating these environments:

• without dedicated platform teams
• using relatively small engineering teams

Overall, production feedback around scalability and operational stability was largely positive.

What are the Operational Challenges Strimzi

Although the operational feedback was generally positive, several recurring challenges were mentioned.

Kubernetes Maintenance and Node Restarts

One commonly mentioned operational issue involved:

• Kubernetes node rotation
• rolling restarts
• Kafka recovery timing during maintenance windows

A frequently recommended mitigation was:

• deploying Strimzi Drain Cleaner

Teams generally described these issues as manageable, but important to plan for operationally.

Upgrade Management

Users also discussed upgrade-related concerns, including:

• Kafka Connect metrics disappearing after upgrades
• migration concerns around deprecated v1beta1 resources
• the importance of validating upgrades carefully

Several users recommended:

• moving to stable APIs
• testing upgrades before production rollout
• validating monitoring behavior after upgrades

Monitoring and Observability

Production teams repeatedly emphasized the importance of monitoring and observability.

Commonly mentioned tooling included:

• JMX metrics
• Prometheus
• Grafana
• alerting pipelines
• JMXTrans

Several teams also highlighted:

• vulnerability scanning
• CVE remediation workflows
• operational monitoring
• production alerting

The operational consensus was that observability is a critical part of successfully running Strimzi in production.

GitOps and Declarative Management

A recurring operational pattern involved managing Kafka infrastructure declaratively.

Teams described:

• storing Kafka custom resources in Git
• deploying through ArgoCD or FluxCD
• managing topics and users declaratively
• automating security configuration

Several users described Git repositories as the operational source of truth for Kafka environments.

Is Strimzi Free

Yes: unlike confluent operator, strimzi is open source and free.

You don't need to buy license, so you will get:

• reduced licensing costs
• operational efficiencies through automation
• benefits for organizations already running Kubernetes

‍

Is strimzi stable? Scalable? Operational manageable?

Most users described Strimzi as:

• stable
• scalable
• production-ready
• operationally manageable

Common feedback included:

• “Everything works fine”
• “No real drawbacks”
• “Very positive experience”
• “Can’t imagine managing this without it”

At the same time, teams consistently emphasized the need for:

• operational readiness
• maintenance planning
• incident management
• monitoring
• recovery procedures

Support for strimzi 1: 0: 0 kafka

Axual provides Strimzi Incident Support services for organizations operating Kafka on Kubernetes with Strimzi, including:

• incident diagnosis and mitigation
• recovery support
• operational assistance for Strimzi-based Kafka environments
• support for Kafka ecosystem components managed through Strimzi
• Silver and Gold support options with defined SLAs and response times

Do you need some support with the Strimzi setup? Learn more about Axual’s Strimzi Incident Support services:
https://axual.com/services/axual-strimzi-incident-support/

Read more on what is new with Strimzi 1-0-0 crd release: https://axual.com/blog/strimzi-1-0-0-crd-versioning-conversion-and-gitops-operations

About Axual

Axual provides services and platform support for organizations running Apache Kafka and Strimzi in Kubernetes environments.

Learn more:
https://axual.com

FAQs

Is Strimzi production ready?

Yes. Strimzi is production ready and is used by many engineering teams to run Apache Kafka on Kubernetes. Like any production Kafka environment, success depends on strong operational practices around monitoring, upgrades, maintenance, incident response, and recovery planning.

Is Strimzi Kubernetes-native?

Yes. Strimzi is designed for Kubernetes-native Kafka operations. It uses Kubernetes custom resources to manage Kafka clusters, topics, users, Kafka Connect, and related components declaratively.

Why do teams use Strimzi?

Teams often use Strimzi because it fits naturally into Kubernetes and GitOps workflows. It helps automate Kafka operations, simplify configuration management, support declarative infrastructure, and make scaling and maintenance easier for teams already running Kubernetes.

Can Strimzi scale Kafka?

Yes. Strimzi can support large-scale Kafka environments. Production users have reported running Strimzi with high message volumes, thousands of topics, large Kafka Connect deployments, multi-region setups, multi-cloud environments, and mTLS-secured clusters.

Is Strimzi stable?

Yes. Production feedback around Strimzi is generally positive. Teams often describe it as stable, scalable, and operationally manageable. However, stability in production still depends on good monitoring, careful upgrade planning, and clear recovery processes.

What are the main operational challenges with Strimzi?

Common challenges include Kubernetes node maintenance, rolling restarts, Kafka recovery during maintenance windows, upgrade validation, monitoring changes after upgrades, and managing deprecated API versions. These challenges are usually manageable, but they need to be planned for.

What is Strimzi Drain Cleaner?

Strimzi Drain Cleaner helps manage Kubernetes node draining more safely for Kafka workloads. It is often recommended when teams need to handle Kubernetes maintenance, node rotation, and rolling restarts in production Strimzi environments.

How do teams manage Strimzi with GitOps?

Many teams store Strimzi custom resources in Git and deploy them through tools such as ArgoCD or FluxCD. This allows Kafka clusters, topics, users, and security configurations to be managed declaratively, with Git as the operational source of truth.

What monitoring is needed for Strimzi in production?

Production Strimzi environments typically need strong observability across Kafka, Kubernetes, and related components. Teams commonly use JMX metrics, Prometheus, Grafana, alerting pipelines, vulnerability scanning, and CVE remediation workflows.

Is Strimzi free?

Yes. Strimzi is open source and free to use. Organizations do not need to buy a Strimzi license, which can help reduce licensing costs, especially for teams already invested in Kubernetes-based operations.

Is Strimzi the same as Confluent for Kubernetes?

No. Strimzi and Confluent for Kubernetes are different approaches to running Kafka on Kubernetes. Strimzi is open source and community-driven, while Confluent for Kubernetes is part of Confluent’s commercial platform.

Do I need a dedicated platform team to run Strimzi?

Not always. Some teams run Strimzi successfully with small engineering teams or without a dedicated Kafka platform team. However, production environments still need clear ownership for monitoring, upgrades, incident handling, and recovery.

What changed with Strimzi 1.0.0?

Strimzi 1.0.0 introduced important changes around CRD versioning and stable APIs. Teams using older resource versions should review their configuration, move to supported APIs, and validate upgrade paths carefully before rolling changes into production.

Does Axual support Strimzi?

Yes. Axual provides Strimzi Incident Support for organizations running Kafka on Kubernetes with Strimzi. This includes incident diagnosis, mitigation, recovery support, and operational assistance for Strimzi-based Kafka environments.

When should I consider Strimzi support?

You should consider Strimzi support if Kafka is business-critical, if your team needs help with incidents, if you are planning upgrades, or if you want expert support around recovery, maintenance, and production readiness.

‍