Merge pull request #110 from warpstreamlabs/increase-default-cpu-requ…

…ests

Increase default CPU requests to 4 from 2

charts/warpstream-agent/CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.13.33] - 2024-10-08
+
+### Added
+
+- Increase default CPU requests from 2 to 4.
+
 ## [0.13.32] - 2024-09-27
 
 ### Added

charts/warpstream-agent/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: warpstream-agent
 description: WarpStream Agent for Kubernetes.
 type: application
-version: 0.13.32
+version: 0.13.33
 appVersion: v587
 icon: https://avatars.githubusercontent.com/u/132156278
 home: https://docs.warpstream.com/warpstream/

charts/warpstream-agent/values.yaml

@@ -67,7 +67,7 @@ config:
 enforceProductionResourceRequirements: true
 resources:
   # Recommendations:
-  #   1. At least 2 requests vCPUs per Agent, and only use whole numbers for CPUs
+  #   1. At least 4 requests vCPUs per Agent, and only use whole numbers for CPUs
   #      because we set GOMAXPROCS to the value of requested CPUs.
   #      The Agents use the value of GOMAXPROCS to determine how many cores they have,
   #      (to avoid throttling) and size caches and other data structures in accordance
@@ -82,14 +82,14 @@ resources:
   #      use-cases.
   #   4. Keep memory requests and limits the same.
   requests:
-    cpu: 2
-    memory: 8Gi
+    cpu: 4
+    memory: 16Gi
     # we do not need the disk space, but Kubernetes will count some logs that it emits
     # about our containers towards our containers ephemeral usage and if we requested
     # 0 storage we could end up getting evicted unnecessarily when the node is under disk pressure.
     ephemeral-storage: "100Mi"
   limits:
-    memory: 8Gi
+    memory: 16Gi
     ephemeral-storage: "100Mi"
 
 extraEnv: []