AnalysisRun Job running in separate namespace not visible in UI

[nardew]

Describe the bug

I am running Argo Rollouts v1.8.3 with ARGO_ROLLOUTS_ANALYSIS_JOB_NAMESPACE environment variable set as described here. When AnalysisRun with job provider is instantiated, the underlying K8s pod runs in the correct namespace (specified in ARGO_ROLLOUTS_ANALYSIS_JOB_NAMESPACE). However, this pod is not visible from the UI even though it belongs to my application. As a consequence, if the job fails, my users have no way to check the logs of the pod.

To Reproduce

Run Argo Rollouts with ARGO_ROLLOUTS_ANALYSIS_JOB_NAMESPACE set and have AnalysisTemplate which triggers a K8s job. The triggered K8s job is not visible in the UI of the Argo application.

Expected behavior

K8s jobs triggered by AnalysisRun in a dedicated namespace (dictated by ARGO_ROLLOUTS_ANALYSIS_JOB_NAMESPACE) are visible in the UI as if they were running in the same namespace as the rollout.

Screenshots

n/a

Version

1.8.3
Logs

# Paste the logs from the rollout controller

# Logs for the entire controller:
kubectl logs -n argo-rollouts deployment/argo-rollouts

# Logs for a specific rollout:
kubectl logs -n argo-rollouts deployment/argo-rollouts | grep rollout=<ROLLOUTNAME

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.