release 0.0.6

Includes:

• Enhancements
  • Bump Splunk Otel Collector from 0.61.0 to 0.71.0 (#257)
  • Bump golang from 1.19.0 to 1.20.0 (#240)
  • Bump go.opentelemetry.io/collector/semconv from 0.59.0 to 0.72.0 (#251)
  • Bump go.opentelemetry.io/otel from 1.10.0 to 1.14.0 (#252)
  • Bump docker/build-push-action from 3.3.0 to 4.0.0 (#239)

0.0.5

Includes:

• Enhancements
  • Upgraded the Splunk Otel Collector to v0.61.0 (#205)
  • Updated K8s SecurityContextConstraints to support Openshift 4.11.x (#203)
  • Add initial base support for deploying gateway collectors (#184)

0.0.4

Includes:

• Enhancements

  • Upgraded Go to v1.19
  • Upgraded the Splunk Otel Collector to v0.58.0
  • Upgraded project dependencies

  Notice:
  Due to issues with uploading operator images to quay.io, this releases will use an operator image from https://hub.docker.com/r/jvsplk/splunk-otel-collector-operator as a work around for now.

0.0.3

Upgrading from 0.0.1

This version is not compatible with the previous 0.0.1 release. Please remove the previous installation completely before installing v0.0.3.

Getting started

1. Ensure Cert Manager is installed and available in your cluster

To install the operator in an existing cluster, make sure you have cert-manager installed and run:

2. Install the Operator

2.a Kubernetes

kubectl apply -f https://github.com/signalfx/splunk-otel-operator/releases/download/v0.0.3/splunk-otel-operator.yaml

2.b OpenShift

oc apply -f https://github.com/signalfx/splunk-otel-operator/releases/download/v0.0.3/splunk-otel-operator-openshift.yaml

3. Add your Splunk APM token

kubectl create secret generic splunk-access-token --namespace splunk-otel-operator-system --from-literal=access-token=SPLUNK_ACCESS_TOKEN

4. Deploy Splunk OpenTelemetry Connector

Once the splunk-otel-operator-controller-manager deployment is ready, install the Splunk Otel Agent as follows:

$ kubectl apply -f - <<EOF
apiVersion: otel.splunk.com/v1alpha1
kind: Agent
metadata:
  name: splunk-otel
  namespace: splunk-otel-operator-system
spec:
  clusterName: <MY_CLUSTER_NAME>
  splunkRealm: <SPLUNK_REALM>
EOF

Replace MY_CLUSTER_NAME and SPLUNK_REALM with your values.

WARNING: Until the OpenTelemetry Collector format is stable, changes may be required in the above example to remain
compatible with the latest version of the Splunk OpenTelemetry Operator and Splunk OpenTelemetry Connector.

0.0.2

Upgrading from 0.0.1

This version is not compatible with the previous 0.0.1 release. Please remove the previous installation completely before installing v0.0.2.

Getting started

1. Ensure Cert Manager is installed and available in your cluster

To install the operator in an existing cluster, make sure you have cert-manager installed and run:

2. Install the Operator

2.a Kubernetes

kubectl apply -f https://github.com/signalfx/splunk-otel-operator/releases/download/v0.0.2/splunk-otel-operator.yaml

2.b OpenShift

oc apply -f https://github.com/signalfx/splunk-otel-operator/releases/download/v0.0.2/splunk-otel-operator-openshift.yaml

3. Add your Splunk APM token

kubectl create secret generic splunk-access-token --namespace splunk-otel-operator-system --from-literal=access-token=SPLUNK_ACCESS_TOKEN

4. Deploy Splunk OpenTelemetry Connector

Once the splunk-otel-operator-controller-manager deployment is ready, install the Splunk Otel Agent as follows:

$ kubectl apply -f - <<EOF
apiVersion: otel.splunk.com/v1alpha1
kind: Agent
metadata:
  name: splunk-otel
  namespace: splunk-otel-operator-system
spec:
  clusterName: <MY_CLUSTER_NAME>
  splunkRealm: <SPLUNK_REALM>
EOF

Replace MY_CLUSTER_NAME and SPLUNK_REALM with your values.

WARNING: Until the OpenTelemetry Collector format is stable, changes may be required in the above example to remain
compatible with the latest version of the Splunk OpenTelemetry Operator and Splunk OpenTelemetry Connector.

v0.0.1

Getting started

1. Ensure Cert Manager is installed and available in your cluster

To install the operator in an existing cluster, make sure you have cert-manager installed and run:

2. Install the Operator

2.a Kubernetes

kubectl apply -f https://github.com/signalfx/splunk-otel-operator/releases/download/v0.0.1/splunk-otel-operator.yaml

2.b OpenShift

oc apply -f https://github.com/signalfx/splunk-otel-operator/releases/download/v0.0.1/splunk-otel-operator-openshift.yaml

3. Add your Splunk APM token

kubectl create secret generic splunk-access-token --namespace splunk-otel-operator-system --from-literal=access-token=SPLUNK_ACCESS_TOKEN

4. Deploy Splunk OpenTelemetry Connector

Once the splunk-otel--operator deployment is ready, create an Splunk OpenTelemetry Collector instance, like:

$ kubectl apply -f - <<EOF
apiVersion: splunk.com/v1alpha1
kind: SplunkOtelAgent
metadata:
  name: splunk-otel
  namespace: splunk-otel-operator-system
spec:
  clusterName: <MY_CLUSTER_NAME>
  splunkRealm: <SPLUNK_REALM>
EOF

Replace MY_CLUSTER_NAME and SPLUNK_REALM with your values.

WARNING: Until the OpenTelemetry Collector format is stable, changes may be required in the above example to remain
compatible with the latest version of the Splunk OpenTelemetry Operator and Splunk OpenTelemetry Connector.