fix: cluster workflow template store is not initialized in namespace mode. Fixes #14763#14766
Conversation
Signed-off-by: Eduardo Rodrigues <eduardodbr@hotmail.com>
|
even with this patch, i get a nil-pointer error when trying to use the api client on a cluster where i have no access to Stack Traceit seems that the |
|
@eduardodbr i might provide a PR on top of your PR if that's cool? |
|
Sure go ahead |
…vailable to the API client Signed-off-by: Marcus Weiner <marcus.weiner@gmail.com>
|
here is my added fix: eduardodbr#1 If it doesn't make sense to integrate it into this PR, i'm happy to do it against the main repo |
|
@mraerino can you provide a reproducible example to test? thanks |
|
Here is some code to reproduce:
|
fix: avoid nil-pointer access when clusterworkflowtemplates are not available
…lowTemplate when RBAC is not enabled Signed-off-by: Eduardo Rodrigues <eduardodbr@hotmail.com>
|
@mraerino thank you for your contribution. I have made a small change to also make sure argo server always starts clusterworkflowtemplate store |
|
Hi, |
terrytangyuan
left a comment
There was a problem hiding this comment.
LGTM. Thanks for the fix!
Fixes #14763
Motivation
Submitting a workflow via UI, either from workflow template or via cron workflow, in namespace mode is failing because the informer is not initialized.
Modifications
The template store is always initialized to NullClusterWorkflowTemplate when RBAC is not enabled.
Verification
Run with namespace-install.yaml.
Submited via:
kubectl create
Argo submit
Cron submit via UI
Workflow template submit via UI
argoKubeClient
Documentation