Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add agentGroups, extraEnvFrom, and update image #165

Merged
merged 4 commits into from
Jan 23, 2025
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions charts/warpstream-agent/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [0.13.75] - 2025-01-22

- Update WarpStream Agent to v614.
- Add native support for agent groups https://docs.warpstream.com/warpstream/byoc/advanced-agent-deployment-options/agent-groups
- Add value array `extraEnvFrom` to add more items to the `envFrom` field.

## [0.13.75] - 2025-01-22

- Update WarpStream Agent to v613.

## [0.13.74] - 2025-01-16
Expand Down
4 changes: 2 additions & 2 deletions charts/warpstream-agent/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@ apiVersion: v2
name: warpstream-agent
description: WarpStream Agent for Kubernetes.
type: application
version: 0.13.75
appVersion: v613
version: 0.13.76
appVersion: v614
icon: https://avatars.githubusercontent.com/u/132156278
home: https://docs.warpstream.com/warpstream/
sources:
Expand Down
26 changes: 26 additions & 0 deletions charts/warpstream-agent/ci/playground-agent-group-values.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
config:
playground: true
agentGroup: "my-group"

deploymentStrategy:
type: RollingUpdate
rollingUpdate: null # setting rollingUpdate to null so helm will fail if pod doesn't start

# overriding resources so it fits on a runner
resources:
requests:
cpu: 1
memory: 4Gi
# 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: 4Gi

kafkaService:
enabled: true

extraEnv:
- name: WARPSTREAM_ADVERTISE_HOSTNAME_STRATEGY
value: auto-ip4 # playground mode defaults to local so we need to override it for tests to pass
6 changes: 6 additions & 0 deletions charts/warpstream-agent/templates/deployment.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,9 @@ spec:
{{- end }}
{{- end }}
{{- end }}
{{- if .Values.config.agentGroup }}
- -agentGroup={{ .Values.config.agentGroup }}
{{- end }}
readinessProbe:
httpGet:
path: /v1/status
Expand Down Expand Up @@ -154,6 +157,9 @@ spec:
- secretRef:
name: {{ include "warpstream-agent.secretName" . }}
{{- end }}
{{- with .Values.extraEnvFrom }}
{{ toYaml . | nindent 12 }}
{{- end }}
ports:
- name: kafka
containerPort: 9092
Expand Down
12 changes: 12 additions & 0 deletions charts/warpstream-agent/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,9 @@ config:
# apiKeySecretKeyRef: # Provide this if you want to manage the secret externally
# name:
# key:
# Agent Groups configuration https://docs.warpstream.com/warpstream/byoc/advanced-agent-deployment-options/agent-groups
# Leave empty for Default group
agentGroup: ""

# Ensures that the Agents are configured with the recommended resources for production
# usage. We recommend that you do not set this to false except for in staging/dev
Expand Down Expand Up @@ -164,6 +167,15 @@ extraEnv: []
# Add additional environment settings to the pod. Can be useful in proxy
# environments

extraEnvFrom: []
# Add additional environment from configmaps or secrets.
# Example:
# extraEnvFrom:
# - configMapRef:
# name: my-env-from-configmap
# - secretRef:
# name: my-env-from-secret

volumeMounts: []
# Add any volumeMounts to the pod.

Expand Down
Loading