Mor Dadon Kaye

We are also experiencing this. Running on multiple clusters while only 2 of them seem to have this issue.

I think the problem is with the [GetAll()](https://github.com/stakater/IngressMonitorController/blob/b8935463de6b2bd17aa2cf8b1b4defa3ebedf576/pkg/monitors/monitor-service.go#L11) function. Maybe it should also return an error, that way if an error is returned from it the reconciliation loop should continue...

Hey guys, this is still happening, are you willing to accept a PR for this?

Google have updated their docs and now explain why this is happening. Apparently setting 'Uniform Bucket Level Access' to true is a requirement when using IAM principals for Workload Identity...

We are experiencing the same issue. We have configured stargz-snapshotter with containerd as described in the docs. The supplied pre built images are pulling lazily with no issues (can confirm...

> > docker.io/dadavan/python:3.10-esgz": 4 error(s) occurred:\n\t* gzip: invalid header\n\t* legacy: failed to get footer gzip reader: gzip: invalid header\n\t* invalid magic number\n\t* gzip: invalid header: failed to resolve target >...

> @Dadavan > > > docker > > Does using other image tools (e.g. [`crane`](https://github.com/google/go-containerregistry)) or other registry (e.g. ghcr.io) solve the issue? > > > docker buildx build -t...

The same thing happens for `prometheuses.monitoring.coreos.com` (prometheus-operator). The fields `PrometheusSpecResourcesLimitsArgs` and `PrometheusSpecResourcesRequestsArgs` are empty structs. They [follow the same pattern](https://github.com/prometheus-operator/prometheus-operator/blob/main/jsonnet/prometheus-operator/prometheuses-crd.json#L1976) as the above, i.e: ``` anyOf: - type: integer -...