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.

Sign up for GitHub

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

Jump to bottom

Configure operate correctly #84

Merged
merged 4 commits into from
Aug 24, 2023
Merged

Configure operate correctly #84

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1a2e2f2
feat: configure operate correctly
Zelldon Aug 23, 2023
d342816
test: update golden files
Zelldon Aug 24, 2023
bfec0e2
test: add operate golden test
Zelldon Aug 24, 2023
77fd016
test: update golden files
Zelldon Aug 24, 2023
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
25 changes: 22 additions & 3 deletions charts/zeebe-benchmark/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,11 +318,11 @@ camunda-platform:
# RetentionPolicy.zeebeIndexMaxSize can be set to configure the maximum allowed zeebe index size in gigabytes.
# After reaching that size, curator will delete that corresponding index on the next run.
# To benefit from that configuration the schedule needs to be configured small enough, like every 15 minutes.
zeebeIndexMaxSize: 1
zeebeIndexMaxSize: 30
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ This is to not delete data too early.

# RetentionPolicy.operateIndexTTL defines after how many days an operate index can be deleted
operateIndexTTL: 30
operateIndexTTL: 1
# RetentionPolicy.tasklistIndexTTL defines after how many days a tasklist index can be deleted
tasklistIndexTTL: 30
tasklistIndexTTL: 1

# Image configuration for the elasticsearch curator cronjob
# https://hub.docker.com/r/bitnami/elasticsearch-curator-archived/tags
Expand All @@ -336,6 +336,25 @@ camunda-platform:

operate:
enabled: false
image:
tag: 8.2.8
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💭 Do we really want to fix the Operate version? Shouldn't we use the same version as we use for the rest of camunda-platform?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually we don't want to fix it, but we might need to set it separately in the benchmark workflows. We also need to make sure they can create docker images on the fly. Which is an open TODO https://github.com/camunda/operate/issues/5178

# Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits
resources:
requests:
cpu: 600m
memory: 400Mi
limits:
cpu: 2000m
memory: 2Gi
env:
- name: OPERATE_LOG_APPENDER
value: Stackdriver
- name: OPERATE_LOG_STACKDRIVER_SERVICENAME
value: operate
- name: OPERATE_LOG_STACKDRIVER_SERVICEVERSION
valueFrom:
fieldRef:
fieldPath: metadata.namespace

tasklist:
enabled: false
Expand Down
Loading