`kubectl get wf` returns workflows not returned by API

madhur-lyric commented 3 months ago

Pre-requisites

[X] I have double-checked my configuration
[X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

kubectl get wf -n {namespace} returns some workflows not found in the workflows or archived workflows API (fetched without any parameters), but they are returned when fetched or deleted individually using the API: api/v1/workflows/{namespace}/{workflow-name}.

Version(s)

v3.5.8

Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

N.A.

Logs from the workflow controller

kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

Logs from in your workflow's wait container

kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

madhur-lyric commented 2 months ago

@agilgur5 Please share some insights on this issue.

Joibel commented 2 months ago

Can you show how we could reproduce this issue?

argoproj / argo-workflows

`kubectl get wf` returns workflows not returned by API #13346