# Quickstart for distributed connector in kubernetes, connect-0 OOMKilled

**URL:** <https://forum.confluent.io/t/quickstart-for-distributed-connector-in-kubernetes-connect-0-oomkilled/37430>\
**Category:** Self-Managed Connectors\
**Created:** [6 March 2025 22:50 UTC](https://forum.confluent.io/t/quickstart-for-distributed-connector-in-kubernetes-connect-0-oomkilled/37430 "2025-03-06T22:50:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikereiche](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mikereiche/32/4979_2.png) [@mikereiche](https://forum.confluent.io/u/mikereiche)\
**Post date:** [6 March 2025 22:50 UTC](https://forum.confluent.io/t/quickstart-for-distributed-connector-in-kubernetes-connect-0-oomkilled/37430/1 "2025-03-06T22:50:23Z")

</div>

I’m following the instructions here - [Confluent for Kubernetes Quick Start | Confluent Documentation](https://docs.confluent.io/operator/current/co-quickstart.html#co-quickstart-zk). When I get 4.3, all the nodes are ok except…

connect-0 0/1 CrashLoopBackOff 11 (43s ago) 50m

```
Last State: Terminated
  Reason: OOMKilled

```

---

<div class="post-metadata">

**Author:** ![mmuehlbeyer](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mmuehlbeyer/32/1088_2.png) [@mmuehlbeyer](https://forum.confluent.io/u/mmuehlbeyer)\
**Post date:** [10 March 2025 06:52 UTC](https://forum.confluent.io/t/quickstart-for-distributed-connector-in-kubernetes-connect-0-oomkilled/37430/2 "2025-03-10T06:52:30Z")

</div>

did you check the nodes of your underlying K8s cluster?

---

<div class="post-metadata">

**Author:** ![mikereiche](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mikereiche/32/4979_2.png) [@mikereiche](https://forum.confluent.io/u/mikereiche)\
**Post date:** [10 March 2025 19:03 UTC](https://forum.confluent.io/t/quickstart-for-distributed-connector-in-kubernetes-connect-0-oomkilled/37430/3 "2025-03-10T19:03:49Z")

</div>

I was running on an EC2 instance that had 32G memory. Switching to a 72GB EC2 instance it no longer gets OOM. I did not see that in the prerequisites. I started at the URL in the README.md

> Confluent for Kubernetes is a complete, declarative API for deploying and operating Confluent Platform as a cloud-native system on Kubernetes.
> 
> Documentation for this is provided at [Deploy and Manage Confluent Platform Using Confluent for Kubernetes | Confluent Documentation](https://docs.confluent.io/operator/current/overview.html) .
> 
> This package includes the following:
> 
> - The Helm Chart to deploy Confluent for Kubernetes

And then the QuickStart link.

> **[Confluent for Kubernetes Quick Start | Confluent Documentation](https://docs.confluent.io/operator/current/co-quickstart.html)**
>
> Learn how to quickly deploy a Confluent Platform using Confluent for Kubernetes.

---

<div class="post-metadata">

**Author:** ![mmuehlbeyer](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mmuehlbeyer/32/1088_2.png) [@mmuehlbeyer](https://forum.confluent.io/u/mmuehlbeyer)\
**Post date:** [11 March 2025 08:29 UTC](https://forum.confluent.io/t/quickstart-for-distributed-connector-in-kubernetes-connect-0-oomkilled/37430/4 "2025-03-11T08:29:01Z")

</div>

I think 32GB should have been enough at least for testing.  
looks strange a bit

though for prod deployments there are some recommendations

> **[Confluent Platform System Requirements | Confluent Documentation](https://docs.confluent.io/platform/current/installation/system-requirements.html#hardware)**