Alan Clucas
Alan Clucas
Actually, in my case at least, I can issue the query to prom adapter with any namespace (even a non-existent one), and it'll return the correct value for that metric.
This does not work because [the docs](https://argoproj.github.io/argo-workflows/lifecyclehook/#unsupported-conditions) say it should not work. What does work (counter to the docs perhaps) is ``` - - name: step-1 template: output - -...
It seems this is only happening with kubernetes version 1.27 or later. Does anyone have evidence of it happening on earlier versions? We are still using client-go from 0.24, which...
@ljyanesm there is already a PR in progress #12597 for the documentation for this. Please feel free to review and add your perspective on it.
I am unsure if this can be covered under transient error handling. My understanding of this: Transient error handling is where we attempt a network call, and the result of...
> retries are enabled but this did not retry like i expected it would Ok, that's unexpected, I would have expected this to be retried.
If the node `Failed` then your expression requires the `exitCode` to be `255`. Can you verify that was the case?
In which case the controller is doing the right thing, isn't it? It will evaluate your `expression` AND `policy: Always`, but your expression is false, so it won't retry.
@LukasLJL, you'll need to undo the changes to `.spelling` for this to pass CI checks.
I get the same result on 3.4.7