Merge helm charts#80
Conversation
Codecov Report
@@ Coverage Diff @@
## main #80 +/- ##
=========================================
Coverage 70.59% 70.59%
Complexity 154 154
=========================================
Files 29 29
Lines 1146 1146
Branches 57 57
=========================================
Hits 809 809
Misses 285 285
Partials 52 52
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
|
||
| SUB_PROJECTS_DIRS="./hypertrace-alert-engine ./metric-anomaly-task-manager" | ||
|
|
||
| subcommand=$1; shift |
There was a problem hiding this comment.
Why is there a script here? Please use the shared github actions:
Example of packing and publishing:
https://github.com/hypertrace/config-service/blob/777df107b0141eb3368516c6527b4b846ea2d539/.github/workflows/publish.yml#L58-L62
Example of validating:
https://github.com/hypertrace/config-service/blob/777df107b0141eb3368516c6527b4b846ea2d539/.github/workflows/pr-test.yml#L68-L69
| @@ -0,0 +1,7 @@ | |||
| {{- define "metricanomalydetector.image" -}} | |||
There was a problem hiding this comment.
could probably share this if you wanted to, same logic as earlier.
| @@ -65,7 +65,7 @@ spec: | |||
| - name: LOG4J_CONFIGURATION_FILE | |||
| value: "/var/{{ .Chart.Name }}/log/log4j2.properties" | |||
| - name: JAVA_TOOL_OPTIONS | |||
There was a problem hiding this comment.
JAVA_TOOL_OPTIONS shouldn't be used, use JAVA_OPTS instead https://github.com/hypertrace/config-service/blob/777df107b0141eb3368516c6527b4b846ea2d539/helm/templates/deployment.yaml#L65-L66
| initialDelaySeconds: {{ int .Values.livenessProbe.initialDelaySeconds }} | ||
| periodSeconds: {{ int .Values.livenessProbe.periodSeconds }} | ||
| initialDelaySeconds: {{ int .Values.metricAnomalyTaskManagerConfig.livenessProbe.initialDelaySeconds }} | ||
| periodSeconds: {{ int .Values.metricAnomalyTaskManagerConfig.livenessProbe.periodSeconds }} |
There was a problem hiding this comment.
This is outside the scope of this PR, but switching to real probes rather than these TCP probes is something we should work to do on any new service. Series of PRs where I added to attribute service:
hypertrace/attribute-service#100
hypertrace/attribute-service#101
hypertrace/attribute-service#102
There was a problem hiding this comment.
| notificationChannelsConfig: | ||
| name: hypertrace-alert-engine-notification-channels-config | ||
| channels: | ||
| [ |
There was a problem hiding this comment.
These examples shouldn't be in the values
There was a problem hiding this comment.
they can be kept empty and finally be overridden by the user?
There was a problem hiding this comment.
These are the defaults right? generally, these would be created by users at runtime, not as server config.
There was a problem hiding this comment.
these are default file based rules (have to be passed through helm override)
|
|
||
| queryService: | ||
| host: query-service | ||
| port: 9012 |
There was a problem hiding this comment.
values should be based on the standalone ports
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
aaron-steinfeld
left a comment
There was a problem hiding this comment.
Admittedly just did a quick scan, but seems fine. Assuming the configs themselves were previously reviewed.
|
|
||
| - name: validate charts | ||
| run: ./.github/workflows/helm.sh validate No newline at end of file | ||
| args: build -x avroCompatibilityCheck dockerBuildImages No newline at end of file |
There was a problem hiding this comment.
why is the compatibility check disabled?
There was a problem hiding this comment.
Since the avro was not published, will enable.
hypertrace/hypertrace#318