Releases: solarwinds/swi-k8s-opentelemetry-collector
Releases · solarwinds/swi-k8s-opentelemetry-collector
0.10.0
What's Changed
- Replaced OTEL Collector Builder with committed source code by @gantrior in #580
- Upgrade OTEL Collector and 3rd party Docker images by @pstranak-sw in #579
- Updated OTEL collector from 0.91.0 to 0.98.0. Included bugfixes from the upstream OTEL collector processors into the local ones.
- Updated runtime to Go 1.22. The OTEL Collector dropped support for Go 1.20 (that version is out of support). Since Go 1.21 and 1.22 support the same relevant operating systems and platforms, we could just switch to 1.22.
⚠️ Droped support for several Windows versions that are out of support. The minimum requirement is now Windows 10 or Windows Server 2016. This is caused by the update of Go (and OTEL Collector).- Removed Docker image attestations from the built images. Some security scanners could not process the images because of them.
Full Changelog: 0.9.2...0.10.0
swo-k8s-collector-3.3.0-alpha.5
Added
- Added option to configure
nodeSelector
andaffinity
for SWO Agent.
Changed
- Added environment variables
CLUSTER_UID
,CLUSTER_NAME
andMANIFEST_VERSION
to the SWO Agent StatefulSet. Future SWO Agent plugins may include them in their metrics. - Upgraded collector image to
0.10.0
which brings following changes:- See Release notes for 0.10.0.
- Bumped 3rd party dependencies and Docker images.
- Upgraded OTEL Collector to v0.98.0.
⚠️ Dropped support for several Windows versions that are out of support. The minimum requirement is now Windows 10 or Windows Server 2016. This is caused by the update of Go (and the OTEL Collector).
swo-k8s-collector-3.3.0-alpha.4
Changed
- Added validation schema for the provided Helm chart configuration.
swo-k8s-collector-3.3.0-alpha.3
Changed
- Container logs from AWS EKS Fargate clusters are now sent to SWO as-is.
fluentbit.io/parser
andfluentbit.io/exclude
annotations are ignored. This both fixes an issue with "empty" JSON logs sent to SWO and aligns the behavior with non-Fargate container logs.
This change is applied only to Pods that are started after the newk8s collector
is deployed to the k8s cluster.
swo-k8s-collector-3.3.0-alpha.2
Fixed
- Fixed Journal log collection on EKS (and other environments where journal logs are stored in
/var/log/journal
)
swo-k8s-collector-3.3.0-alpha.1
Added
- Added an option to configure
timeout
for each attempt to send data to SWO.- The default value is
15s
(previously it was5s
) to avoid unnecessary retries when the backend takes time to respond.
- The default value is
Changed
- Add validation of the OTEL endpoint provided in
values.yaml
. In case a deprecated endpoint is detected, report a warning during chart installation/update.
swo-k8s-collector-3.2.0
Added
- Added Linux ARM64 support
- Added Windows Server 2019 support
- Added option to deploy OpenCost collector
- Can be enabled by setting
openconst.enabled
totrue
invalues.yaml
- Can be enabled by setting
- Added option to pull images from ACR by setting
global.azure.images.<image_key>
invalues.yaml
when running in AKS - Added
otel.api_token
to allow setting API token for OTEL collector throughvalues.yaml
- Added
otel.metrics.autodiscovery.prometheusEndpoints.podMonitors
configuration option. Define if you want to monitor applications that do not have Prometheus annotations. - Started publishing custom Istio metrics, when available:
k8s.istio_request_bytes.delta
,k8s.istio_response_bytes.delta
,k8s.istio_requests.rate
,k8s.istio_tcp_sent_bytes.rate
,k8s.istio_tcp_received_bytes.rate
,k8s.istio_requests.delta
,k8s.istio_tcp_sent_bytes.delta
,k8s.istio_tcp_received_bytes.delta
,k8s.istio_request_bytes.rate
,k8s.istio_response_bytes.rate
andk8s.istio_request_duration_milliseconds.rate
Changed
- Upgraded OTEL collector image to
0.9.2
which brings following changes - Adjusted node-collector memory limits for better performance
- Removed sha256 from image references to enable multiarch support
- Removed
k8s.kube_daemonset_labels
,k8s.kube_deployment_labels
andk8s.kube_statefulset_labels
metrics (they were redundant anyway)- There are no longer published by the updated
kube-state-metrics
- There are no longer published by the updated
- Stopped sending histogram metrics to SWO
- Added PVC for SWO Agent, when enabled
Fixed
- Fixed autoupdate job
- Fixed usage of
ebpfNetworkMonitoring.k8sCollector.relay.image.pullPolicy
- Fixed restarts of the collector when automatic discovery and scraping of prometheus endpoints (
otel.metrics.autodiscovery.prometheusEndpoints.enabled
) was disabled or enabled on a Fargate environment
swo-k8s-collector-3.2.0-alpha.17
Fixed how k8s.istio_request_duration_milliseconds.rate
metric is calculated
swo-k8s-collector-3.2.0-alpha.15
Fixed
- Fixed restarts of the collector when automatic discovery and scraping of prometheus endpoints (
otel.metrics.autodiscovery.prometheusEndpoints.enabled
) was disabled
swo-k8s-collector-3.2.0-alpha.13
Changed
- Make sure discoverd histogram metrics are not sent to SWO
- Publish custom Istio metrics, when available:
k8s.istio_request_bytes.rate
,k8s.istio_response_bytes.rate
andk8s.istio_request_duration_milliseconds.rate