Allow to deploy multiple instance of SumoLogic in the same Namespace

[asubramanianrl]

We consume the SumoLogic in the EU/US region so basically, everything is an individual entity. we want to deploy the Sumologic collector of both EU/US in the same namespace.

Error: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "sumologic-configmap" in namespace "xxx" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "sumologic-us-collector": current value is "sumologic-eu-collector"

Value File (interchange the value of EU/US)

sumologicSecretName: sumologic-access-secret-eu
sumologicUrl: https://api.eu.sumologic.com/api
accessKeyName: sumologic-eu-access-key
accessIdName: sumologic-eu-access-id

sumologic:
  fullnameOverride: "sumo-col-eu"
  sumologic:
    setupEnabled: true
    envFromSecret: sumologic-access-secret-eu
    traces:
      enabled: true
      spans_per_request: 100

Due to static configmap, the deploy is breaking. https://github.com/SumoLogic/sumologic-kubernetes-collection/blob/main/deploy/helm/sumologic/templates/chart-configmap.yaml

• Collection version: 3.8.0

[andrzej-stencel]

If you deploy the Sumo Logic Kubernetes Collection twice in the same cluster (in the same namespace or not), you will end up with a lot of duplicate resources and likely duplicated telemetry.

• Two daemonsets reading logs from pods - causing duplicate logs,
• Two node-exporter daemonsets, two kube-state-metrics deployments, two metrics collectors - causing duplicate metrics.

It seems you are trying to solve a problem or satisfy a requirement, but I'm not convinced deploying the Sumo Logic Kubernetes Collection chart twice in the same cluster is the solution.

Can you describe the requirement/problem that you experience that deploying a single instance of the collection chart does not solve?

Is it that you want to send the same logs and/or metrics to two separate Sumo Logic backends - one in the US (https://service.sumologic.com/) and one in Europe (https://service.eu.sumologic.com/)?

[asubramanianrl]

Thanks for the reply. At the moment, we want to send the OpenTelemetry Trace to the SumoLogic. We are using the https://service.us2.sumologic.com and https://service.eu.sumologic.com.

A few services want to send the traces to the EU instances and others want to send them to the US Instances.

I understand that the nature of the daemonsets runs in the cluster level so we can't deploy the multiple instances of the SumoLogic in the same cluster.