Releases: SumoLogic/sumologic-kubernetes-collection
v3.9.1
v3.9.0
Released 2023-06-14
Breaking Changes
-
feat(metrics)!: disable remote write proxy access logs by default #3071
The logs can be enabled by setting
sumologic.metrics.remoteWriteProxy.config.enableAccessLogs
totrue
.
Added
- fix: otelcol logs json_merge where message bodies are only sometimes json #3050
Changed
-
feat: override namespace from values #3068
-
chore: upgrade Fluent Bit to 2.1.4 #3075 This change may break some custom Fluent Bit configurations.
A temporary workaround is to switch back to the 1.6.10-sumo-3 image. We recommend updating the custom configuration, or better yet,
switching to Otel. -
feat: pass extra arguments to otel logs statefulset #3076
-
Reordering HPA metrics to match HPA ordering #3078
-
chore: drop support for k8s 1.22 #3081
Fixed
v3.8.0
Released 2023-05-22
Added
- feat(metrics): add experimental otel metrics collector #2988
- feat: allow setting otelcol image globally #3051
- feat: add optional fips suffix for otelcol images #3056
- feat: Add multiline support to EKS Fargate #3059
- feat(metric): allow disabling remote write proxy access logs #3062
Changed
- feat(pvc-cleaner): run pvcCleaner as non-root user #3055
Fixed
- fix: warn about release name length #3054
v3.7.0
v3.6.1
v3.6.0
Released 2023-05-04
Added
- feat: Support for collecting metrics, logs, events and traces on EKS fargate (experimental) with documentation updates #2982
Changed
- chore: add support for KOPS 1.26, EKS 1.25, AKS 1.26, OpenShift 4.12; remove support for GKE 1.21, EKS 1.21, AKS 1.23 #2969
- chore: update setup image to 3.8.0 #3000
- chore: upgrade opentelemetry-operator chart to 0.27.0 #3008
Fixed
- fix: fix logs pipeline if systemd is disabled #3001
v3.5.0
v3.4.0
v3.3.0
Released 2023-03-01
Added
- feat(chart): add
pvcCleaner
#2796
Changed
-
chore(otoperator): update opentelemetry operator, add instrumentation customization #2894
OpenTelemetry-Operator was updated to v0.24.0. New configuration flags were added:- Flags to control metrics/traces export from specific instrumentation in
Instrumentation
resource.opentelemetry-operator.instrumentation.dotnet.metrics.enabled
opentelemetry-operator.instrumentation.dotnet.traces.enabled
opentelemetry-operator.instrumentation.java.metrics.enabled
opentelemetry-operator.instrumentation.java.traces.enabled
opentelemetry-operator.instrumentation.python.metrics.enabled
opentelemetry-operator.instrumentation.python.traces.enabled
- Flags to set CPU and Memory requests and limits for OpenTelemetry-Operator
opentelemetry-operator.manager.resources.limits.cpu
opentelemetry-operator.manager.resources.limits.memory
opentelemetry-operator.manager.resources.requests.cpu
opentelemetry-operator.manager.resources.requests.memory
Warning > This action is required only if you have enabled
opentelemetry-operator
withopentelemetry-operator.enabled: true
.
Please delete the following resources before update of the chart:opentelemetry-operator-validating-webhook-configuration
(validatingwebhookconfiguration)opentelemetry-operator-mutating-webhook-configuration
(mutatingwebhookconfiguration)opentelemetry-operator-controller-manager-metrics-service
(service)opentelemetry-operator-webhook-service
(service)opentelemetry-operator-controller-manager
(deployment)
- Flags to control metrics/traces export from specific instrumentation in
-
chore(metrics): remove deprecated apiserver metrics #2898
Fixed
v3.2.0
Released 2023-02-16
Changed
- feat: disable otel storage compaction on start #2870
- chore: upgrade otelcol to 0.71.0-sumo-0 #2872
- feat: use /tmp for otel storage compaction #2873
- chore: bump setup image to 3.6.0 #2882
Fixed
- feat(instrumentation): scrape label added and updated #2875
Full Changelog: v3.1.0...v3.2.0