bumped terraform on sumologic's provider terraform

Author: samiura

deploy/helm/sumologic/conf/setup/main.tf

@@ -2,7 +2,7 @@ terraform {
   required_providers {
     sumologic = {
       source  = "sumologic/sumologic"
-      version = ">= 3.0.9, < 3.1.0"
+      version = "3.0.12"
     }
     kubernetes = {
       source  = "hashicorp/kubernetes"

deploy/helm/sumologic/myvalues.yaml

@@ -0,0 +1,83 @@
+sumologic:
+  accessId: sukfAAu9YwLxSD
+  accessKey: sdsp8iClNyxic5nk7xD227tszMfj9of5GbveQ2UvlP6iyJ9hRIXdCHrexXSY4NJu
+  endpoint: https://long-api.sumologic.net/api/v1/
+  clusterName: vagrant-box-sa
+  scc:
+    create: true
+
+otellogs:
+  daemonset:
+    containers:
+      otelcol:
+        securityContext:
+          privileged: true
+    initContainers:
+      changeowner:
+        securityContext:
+          privileged: true
+
+tailing-sidecar-operator:
+  enabled: true
+
+kube-prometheus-stack:
+  prometheus-node-exporter:
+    service:
+      port: 9200
+      targetPort: 9200
+
+  prometheusOperator:
+    denyNamespaces:
+    - openshift-apiserver
+    - openshift-apiserver-operator
+    - openshift-authentication
+    - openshift-authentication-operator
+    - openshift-cloud-credential-operator
+    - openshift-cluster-machine-approver
+    - openshift-cluster-samples-operator
+    - openshift-cluster-storage-operator
+    - openshift-cluster-version
+    - openshift-config-operator
+    - openshift-console-operator
+    - openshift-controller-manager
+    - openshift-controller-manager-operator
+    - openshift-dns,openshift-dns-operator
+    - openshift-etcd-operator
+    - openshift-image-registry
+    - openshift-ingress
+    - openshift-ingress-operator
+    - openshift-insights
+    - openshift-kube-apiserver
+    - openshift-kube-apiserver-operator
+    - openshift-kube-controller-manager
+    - openshift-kube-controller-manager-operator
+    - openshift-kube-scheduler
+    - openshift-kube-scheduler-operator
+    - openshift-kube-storage-version-migrator
+    - openshift-kube-storage-version-migrator-operator
+    - openshift-machine-api
+    - openshift-machine-config-operator
+    - openshift-marketplace
+    - openshift-monitoring
+    - openshift-multus
+    - openshift-oauth-apiserver
+    - openshift-operator-lifecycle-manager
+    - openshift-sdn
+    - openshift-service-ca-operator
+    - openshift-user-workload-monitoring
+
+metrics-server:
+  enabled: true
+  apiService:
+    create: false
+  global:
+    compatibility:
+      ## Compatibility adaptations for Openshift
+      ##
+      openshift:
+        ## @param global.compatibility.openshift.adaptSecurityContext Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation)
+        ##
+        adaptSecurityContext: auto
+
+telegraf-operator:
+  enabled: true