mog
mog
Hi @jayanthvn, I don't think the amount of nodes in the cluster is playing a particular role - our smallest cluster is 10 nodes and the restarting of the `aws-node`...
Agreed, this would be a huge help - the binaries are already built!
I seem to be hitting the same issue on v2.10.3. This is my ApplicationSet: ```yaml apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: promtail namespace: argocd spec: goTemplate: true generators: - matrix:...
> @blade5502 @mogopz I have the same issue and same use case as yours - did you manage to resolve this by any chance? For now I'm just filtering clusters...
I seem to be having the same issue using v6.11.1 of the chart. The `metrics` services are created but the ServiceMonitors are not. ```yaml applicationSet: metrics: enabled: true serviceMonitor: enabled:...
Has there been any progress on this?
To give a little context on point 2 (because I'm also seeing the same alert) it's triggering because after updating Loki config only one ingester pod is restarted.
Are there any workarounds to get deprecated AMIs working with Packer? We're using a set of AMIs from the Marketplace which haven't been updated yet and are all marked deprecated,...
Do you publish the checksums for the v7 files anywhere? I'd like to be able to verify the binary as part of the install in a Docker image.
Sorry, I probably should created an issue on the main `pnpm` repo. I'm wanting to verify the binaries attached to the releases in there (specifically `pnpm-linux-arm64`/`pnpm-linux-amd64`)