trying to install helm chart fails on windows EKS nodes as no windows image are uploaded to registry

[bmanojlovicrival]

Describe the bug A clear and concise description of what the bug is.
Subject
Logs Logs which can be helpful in investigating the issue.

  Normal   Pulling      42m (x4 over 44m)      kubelet            Pulling image "public.ecr.aws/sumologic/sumologic-otel-collector:0.99.0-sumo-0"
  Warning  Failed       42m (x4 over 44m)      kubelet            Error: ErrImagePull
  Normal   BackOff      4m14s (x173 over 43m)  kubelet            Back-off pulling image "public.ecr.aws/sumologic/sumologic-otel-collector:0.99.0-sumo-0"

and logs of docker (nerdctl in my case but not relevant)

(⎈|cluster-with-windows:sumo) me@mac:~> nerdctl pull --platform windows/amd64 public.ecr.aws/sumologic/sumologic-otel-collector:0.99.0-sumo-0
public.ecr.aws/sumologic/sumologic-otel-collector:0.99.0-sumo-0:               resolved       |++++++++++++++++++++++++++++++++++++++|
index-sha256:d564aff28d4ec37f3d7deb39d7ebfa2da223a6a0cefa933002da35a6415c4c7f: downloading    |--------------------------------------|    0.0 B/743.0 B
elapsed: 1.8 s                                                                 total:   0.0 B (0.0 B/s)
FATA[0002] no match for platform in manifest: not found
Error: exit status 1

and working one!

(⎈|cluster-with-windows:sumo) me@mac:~> nerdctl pull --platform windows/amd64 mcr.microsoft.com/windows/servercore:ltsc2019
mcr.microsoft.com/windows/servercore:ltsc2019:                                    resolved       |++++++++++++++++++++++++++++++++++++++|
index-sha256:6fdf140282a2f809dae9b13fe441635867f0a27c33a438771673b8da8f3348a4:    exists         |++++++++++++++++++++++++++++++++++++++|
manifest-sha256:080beda9bc99d9ff6cab9e8144631471936845d1bb61d5a737704665eb9bef87: exists         |++++++++++++++++++++++++++++++++++++++|
config-sha256:c155f777bc38f3ebacbbbb691dca3c690c2d2cec128174107839e036afd85b3a:   exists         |++++++++++++++++++++++++++++++++++++++|
layer-sha256:d8565a0d56182c8ac77f73952365af8f01baa954279c01ee1a17bd648a428f87:    downloading    |+++++++++++++++-----------------------| 190.5 Mi/478.5 MiB
layer-sha256:cb524f6f22159378ea820d234d80ca09b79c2f0cc91315eeef11904e3ff36a21:    downloading    |+++++---------------------------------| 218.0 Mi/1.5 GiB
elapsed: 3.1 s                                                                    total:  408.5  (131.6 MiB/s)

all pods in namespace

NAME                                                              READY   STATUS              RESTARTS   AGE
sumo-kube-state-metrics-cfdbbf87b-xmz2s                           1/1     Running             0          54m
sumo-opentelemetry-operator-74f948c99f-jx4hk                      0/2     ContainerCreating   0          54m
sumo-prometheus-node-exporter-7fclt                               1/1     Running             0          54m
sumo-prometheus-node-exporter-ksbpn                               1/1     Running             0          54m
sumo-prometheus-windows-exporter-4zs4l                            1/1     Running             0          54m
sumo-prometheus-windows-exporter-hljk4                            1/1     Running             0          54m
sumo-prometheus-windows-exporter-pmqpq                            1/1     Running             0          54m
sumo-prometheus-windows-exporter-x6k87                            1/1     Running             0          54m
sumo-sumolog-metrics-collector-0                                  1/1     Running             0          106m
sumo-sumolog-metrics-targetallocator-64c655b47b-6j25v             1/1     Running             0          106m
sumo-sumolog-otelcol-events-0                                     1/1     Running             0          54m
sumo-sumolog-otelcol-instrumentation-0                            1/1     Running             0          54m
sumo-sumolog-otelcol-instrumentation-1                            1/1     Running             0          54m
sumo-sumolog-otelcol-instrumentation-2                            1/1     Running             0          54m
sumo-sumolog-otelcol-logs-0                                       1/1     Running             0          54m
sumo-sumolog-otelcol-logs-1                                       1/1     Running             0          54m
sumo-sumolog-otelcol-logs-2                                       1/1     Running             0          54m
sumo-sumolog-otelcol-logs-collector-56x7t                         1/1     Running             0          54m
sumo-sumolog-otelcol-logs-collector-k7gjp                         1/1     Running             0          54m
sumo-sumolog-otelcol-metrics-0                                    1/1     Running             0          109m
sumo-sumolog-otelcol-metrics-1                                    1/1     Running             0          54m
sumo-sumolog-otelcol-metrics-2                                    1/1     Running             0          54m
sumo-sumolog-otelcol-windows-logs-collector-6c9ng                 0/1     ImagePullBackOff    0          54m
sumo-sumolog-otelcol-windows-logs-collector-762ct                 0/1     ImagePullBackOff    0          54m
sumo-sumolog-otelcol-windows-logs-collector-j9267                 0/1     ImagePullBackOff    0          54m
sumo-sumolog-otelcol-windows-logs-collector-xfjrk                 0/1     ImagePullBackOff    0          54m
sumo-sumolog-traces-gateway-6fd6cf459b-5xvnp                      1/1     Running             0          54m
sumo-sumolog-traces-sampler-645ddbbfbb-nkz4d                      1/1     Running             0          54m

Command used to install/upgrade Collection Direct command which you used to install/upgrade collection.

Configuration Configuration used for Collection e.g. user-values.yaml for helm.
USER-SUPPLIED VALUES:

metadata:
  persistence:
    storageClass: gp3
otellogswindows:
  daemonset:
    nameservers:
    - 10.10.10.10
prometheus-windows-exporter:
  enabled: true
sumologic:
  accessId: ACCESS_ID
  accessKey: ACCESS_KEY
  clusterName: cluster-with-windows
  collectorName: cluster-with-windows
  events:
    persistence:
      persistentVolume:
        storageClass: gp3
  logs:
    collector:
      otellogswindows:
        enabled: true
    enabled: true
  setup:
    monitors:
      notificationEmails: [email protected]

To Reproduce Steps to reproduce the behavior.

Expected behavior A clear and concise description of what you expected to happen.

Environment (please complete the following information):

• Collection version (e.g. helm ls -n sumologic):

helm ls -n sumo
NAME          	NAMESPACE     	REVISION	UPDATED                              	STATUS  	CHART          	APP VERSION
sumo		sumo		11	      	2024-05-13 12:57:56.589819 +0200 CEST	deployed	sumologic-4.7.0	4.7.0

• Kubernetes version (e.g. kubectl version):

Client Version: v1.29.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.3-eks-adc7111

• Cloud provider:
  AWS
• Others:

Anything else do we need to know Add any other context about the problem here, e.g. issue happens only occasionally.

[sumo-drosiek]

We currently do not provide support for Windows and Windows containers. We build windows containers and push them to the AWS ECR repository, but there are not tested and therefore we do not recommend to use them for production environments

Equivalent of public.ecr.aws/sumologic/sumologic-otel-collector:0.99.0-sumo-0 is public.ecr.aws/sumologic/sumologic-otel-collector-dev:0.99.0-sumo-0-rc.2-4-gf706e, but once again, it is not tested and we do not guarantee it will be working as expected

[bmanojlovicrival]

I am so glad that you do not even read release notes of this exact project release, please re-read and answer in same way if you think you are right

[sumo-drosiek]

@bmanojlovicrival I think we have misunderstanding here. We added templates for logs-collector, but this is in experimental state. We do not provide support for it. We also do not build production-ready Windows containers for sumologic-otel-collector right now.

I can help with configuring the collection with dev image if you want to