Skip to content

Commit

Permalink
document 2019/2022 tags (#988)
Browse files Browse the repository at this point in the history
* document 2019/2022 tags

* Don't run integration tests for md changes
  • Loading branch information
rmfitzpatrick authored Oct 23, 2023
1 parent 797b711 commit f0cb8d2
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 2 deletions.
5 changes: 4 additions & 1 deletion .github/workflows/functional_test.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
name: Splunk Platform Functional Test

on: pull_request
on:
pull_request:
paths:
- '!**.md'

jobs:
functional-test:
Expand Down
2 changes: 2 additions & 0 deletions .github/workflows/functional_test_v2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ name: functional-tests

on:
pull_request:
paths:
- '!**.md'
push:
branches: [ main ]

Expand Down
7 changes: 6 additions & 1 deletion docs/advanced-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,11 @@ Splunk OpenTelemetry Collector for Kubernetes supports collection of metrics,
traces and logs (using OTel native logs collection only) from Windows nodes.

All windows images are available in a separate `quay.io` repository:
`quay.io/signalfx/splunk-otel-collector-windows`.
`quay.io/signalfx/splunk-otel-collector-windows` with two release tracking tags
available: `latest` (Server 2019) and `latest-2022` (Server 2022). Version tags
follow the convention of `<appVersion>` (2019) and `<appVersion>-2022` (2022).
The digests for each release are detailed at
https://github.com/signalfx/splunk-otel-collector/releases.

Use the following values.yaml configuration to install the helm chart on Windows
worker nodes:
Expand All @@ -108,6 +112,7 @@ isWindows: true
image:
otelcol:
repository: quay.io/signalfx/splunk-otel-collector-windows
tag: <appVersion>-2022
logsEngine: otel
readinessProbe:
initialDelaySeconds: 60
Expand Down

0 comments on commit f0cb8d2

Please sign in to comment.