Cr4mble

Facing also the same issue. Here is a simple PoC of the error to reproduce it: ``` apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: ingress-nginx-testing namespace: argocd finalizers: - resources-finalizer.argocd.argoproj.io spec:...

As the go1.x runtime is now officially deprecated and will not get any security updates the new runtimes provided.al2 and provided.al2023 need to be supported for golang to run locally.

@itay-grudev can confirm that the backup to s3 is now working with the current state of the helm chart. The wal files are created in the specific s3 bucket. I...

@slig2008 awesome, didn't know that there is an existing workaround for this, that's why i implemented it by myself. My code looks nearly the same except i'm checking also for...

@vitobotta from a security perspective it's absolutely not right to not restrict traffic to the control planes which is exposed via LoadBalancer, i totally agree on that. Would be nice...

> That's interesting. Did you enable proxy protocol on the load balancer? Otherwise I don't understand how the firewall would see the actual IP of the client instead of that...