Starting with version 0.102.0 of the Dash0 Kubernetes Operator, you can configure any number and combination of backends that best fits your requirements and the operator will ensure the collectors send the data to all of them.
Together with the previously released per-namespace export and API sync configuration, this allows a very flexible routing to different backends.
For example, to send the data from one namespace to two different Dash0 datasets and in addition to a gRPC endpoint, you could use the following exports in your Dash0Monitoring config:
12345678910111213141516171819202122apiVersion: operator.dash0.com/v1beta1kind: Dash0Monitoringmetadata:name: dash0-monitoring-resourcenamespace: some-namespacespec:exports:- dash0:endpoint: ingress...dataset: custom-dataset-oneauthorization:...apiEndpoint: https://api..- dash0:endpoint: ingress...dataset: custom-dataset-twoauthorization:...apiEndpoint: https://api..- grpc:endpoint: ......
You can find more details in the operator's documentation.