Skip to content

Commit

Permalink
chore: ci checks
Browse files Browse the repository at this point in the history 
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
  • Loading branch information
@sumo-drosiek
sumo-drosiek committed Jul 20, 2023
1 parent 2012c78 commit f38fd78
Show file tree
Hide file tree
Showing 3 changed files with 23 additions and 13 deletions.
12 changes: 11 additions & 1 deletion deploy/helm/sumologic/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -441,7 +441,12 @@ The following table lists the configurable parameters of the Sumo Logic chart an
| `opentelemetry-operator.instrumentationJobImage.image.tag` | Name of the image tag used to apply Instrumentation resource | `2.14.0` |
| `opentelemetry-operator.admissionWebhooks` | Admission webhooks make sure only requests with correctly formatted rules will get into the Operator. They also enable the sidecar injection for OpenTelemetryCollector and Instrumentation CR's. | See [values.yaml] |
| `opentelemetry-operator.manager.env` | Additional environment variables for opentelemetry-operator helm chart. | `Nil` |
| `otelcolInstrumentation.enabled` | Enables Sumo OTel Distro Collector StatefulSet to collect telemetry data. [See docs for more information.](/docs/opentelemetry-collector.md#traces) | `true` |
| `otelcolInstrumentation.enabled` | Enables Sumo Otel Distro Collector StatefulSet to collect telemetry data. [See docs for more information.](/docs/opentelemetry-collector.md#traces) | `true` |
| `otelcolInstrumentation.autoscaling.enabled` | Option to turn autoscaling on for Sumo Otel Distro Collector StatefulSet and specify params for HPA. Autoscaling needs metrics-server to access cpu metrics. | `false` |
| `otelcolInstrumentation.autoscaling.minReplicas` | Default min replicas for autoscaling. | `3` |
| `otelcolInstrumentation.autoscaling.maxReplicas` | Default max replicas for autoscaling | `10` |
| `otelcolInstrumentation.autoscaling.targetCPUUtilizationPercentage` | The desired target CPU utilization for autoscaling. | `100` |
| `otelcolInstrumentation.autoscaling.targetMemoryUtilizationPercentage` | The desired target memory utilization for autoscaling. | `50` |
| `otelcolInstrumentation.statefulset.replicaCount` | Set the number of otelcol-instrumentation replicasets. | `3` |
| `otelcolInstrumentation.statefulset.nodeSelector` | Node selector for otelcol-instrumentation statefulset. [See docs/best-practices.md for more information.](/docs/best-practices.md) | `{}` |
| `otelcolInstrumentation.statefulset.priorityClassName` | Priority class name for otelcol-instrumentation pods. | If not provided then set to `RELEASE-NAME-sumologic-priorityclass`. |
Expand Down Expand Up @@ -477,6 +482,11 @@ The following table lists the configurable parameters of the Sumo Logic chart an
| `otelcolInstrumentation.statefulset.containers.otelcol.readinessProbe` | Readiness probe settings for the otelcol-instrumentation container. | `{"initialDelaySeconds": 5, "periodSeconds": 10, "timeoutSeconds": 3, "failureThreshold": 3}` |
| `otelcolInstrumentation.statefulset.containers.otelcol.securityContext` | The securityContext configuration for the otelcol-instrumentation container. | `{}` |
| `tracesGateway.enabled` | Flag to control deploying traces-gateway. [See docs for more information.](/docs/opentelemetry-collector.md#traces) | `true` |
| `tracesGateway.autoscaling.enabled` | Option to turn autoscaling on for traces-gateway and specify params for HPA. Autoscaling needs metrics-server to access cpu metrics. | `false` |
| `tracesGateway.autoscaling.minReplicas` | Default min replicas for autoscaling. | `3` |
| `tracesGateway.autoscaling.maxReplicas` | Default max replicas for autoscaling | `10` |
| `tracesGateway.autoscaling.targetCPUUtilizationPercentage` | The desired target CPU utilization for autoscaling. | `100` |
| `tracesGateway.autoscaling.targetMemoryUtilizationPercentage` | The desired target memory utilization for autoscaling. | `50` |
| `tracesGateway.deployment.replicas` | Set the number of OpenTelemetry Collector replicas. | `1` |
| `tracesGateway.deployment.nodeSelector` | Node selector for otelcol deployment. [See docs/best-practices.md for more information.](/docs/best-practices.md) | `{}` |
| `tracesGateway.deployment.priorityClassName` | Priority class name for OpenTelemetry Collector log pods. | `Nil` |
Expand Down
12 changes: 6 additions & 6 deletions tests/helm/testdata/goldenfile/otelcol-instrumentation-hpa/basic.output.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ spec:
minReplicas: 3
maxReplicas: 10
metrics:
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 100
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 100
12 changes: 6 additions & 6 deletions tests/helm/testdata/goldenfile/traces-gateway-hpa/basic.output.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ spec:
minReplicas: 3
maxReplicas: 10
metrics:
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 100
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 100

0 comments on commit f38fd78

Please sign in to comment.