Anton Gilgur
Anton Gilgur
> i also would love to have the UserInfo and ns correct in UI To be clear, this only impacts those using SSO RBAC Namespace Delegation and the current SA...
> This would be a better user experience then a blank input box. It would be, but this is a bit easier said than done. There's actually a separate feature...
Nice analysis! Yes, you're correct that it would have to be added to the `info` endpoint (although it would be better to name it identically). I've also tried to avoid...
> for what reason ever, there is a link to a not existing web-page. https://wails.io/guides/resolving-missing-packages You didn't specify your version, full logs, OS, or where you found this link, but...
Optional distributed tracing support could potentially be good to have. It could be enabled by an environment variable and the collector URL and port can be specified in an environment...
> OpenTelemetry is great. However, it requires users to write the instrument code in Argo workflows. SkyWalking did that work automatically, and inject the code into Argo workflow. So, for...
> Users can choose if send the tracing data to SkyWalking server [via env](https://github.com/apache/skywalking-go/pull/134). Oh cool, I saw that the reporter had a [`discard`](https://github.com/apache/skywalking-go/blob/c4d27b394d31f2313ff7d3078ca75d635e6a1565/tools/go-agent/config/agent.default.yaml#L35) config, no idea that you were...
Saw [this thread in the `#argo-contributors`](https://cloud-native.slack.com/archives/C020XM04CUW/p1699825880000639) Slack channel today and Argo CD apparently implemented OTel already. https://github.com/argoproj/argo-cd/pull/7539 was linked there, but that seems to be for gRPC specifically and it...
> This issue has been discussing in the issue #1229 That issue is itself a duplicate: #1226, #1225, #1221, #1219, #1217