rumstead

> Looks like codecov is uploading, but the coverage amount hasn't changed... will look tomorrow ``` Run go tool covdata percent -i=./test-results -o test-results/full-coverage.out warning: no applicable files found in...

Didn't seem to help. When I run: ``` make install-test-tools-local make start-e2e-local make test-e2e-local ``` I see the `test-results` directory populated ``` ❯ ls test-results/cov* test-results/covcounters.59ea707707b901d5957baf3fc0fa64f0.12281.1715805185934105000 test-results/covcounters.c6bb65ce0a5fa66569a4cb1fc6efc6b4.40502.1717427615343989000 test-results/covcounters.59ea707707b901d5957baf3fc0fa64f0.12294.1715805187074782000 test-results/covcounters.c6bb65ce0a5fa66569a4cb1fc6efc6b4.40504.1717427620834574000 test-results/covcounters.c6bb65ce0a5fa66569a4cb1fc6efc6b4.39184.1717427697662708000...

Ok after looking at the `e2e-server.log` I see the error for all the binaries. ``` 19:20:11 repo-server | error: coverage meta-data emit failed: output directory "test-results" inaccessible (err: stat test-results:...

Relevant discussion: https://github.com/argoproj/argo-cd/issues/17003

It is currently impossible to use the last helm sdk with Argo CD modules

@shivamerla the issue is with using resource quotas. If one is defined, the init containers cannot be admitted. Happy to submit a PR. [LimitRanges](https://kubernetes.io/docs/concepts/policy/limit-range/) is a stopgap but rolling that...

/remove-label lifecycle/stale

I wonder if we set the azure libs to the same ones from the kubelogin go.mod if it will fix it. https://github.com/Azure/kubelogin/blob/9b6ecad1a09cb72d5cd1ad266ac6977553a67811/go.mod#L7

> If I understand correctly v3.0.1 still includes github.com/Azure/kubelogin v0.1.9. My suggestion would be to include a newer version, which corrects the issue. > > Or have an older version...

Cut a new release, 3.0.7. Please reopen if the latest images don't fix the login issues.