You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn’t see the description of Argo apiserver in your document. If I use this addon, does it mean that the argo api client I am currently using no longer works and I need to change to using k8s native api to create workflows?
The text was updated successfully, but these errors were encountered:
Please keep in mind I am not an Argo Workflow developer. I did this project in collaboration with the Argo Workflow maintainers @sarabala1979 and @juliev0 trying to bring multicluster management to Argo Workflow using OCM-io.
In this project description setup, the main hub cluster only contains the Argo Workflow related CRDs. Since the hub cluster doesn't have the Argo deployments, your Argo API client most likely wouldn't be able to interact with it directly.
However, in @sarabala1979 and @juliev0 more complete setup. I think they had all the Argo Workflow deployments (api server, crds etc) on the hub cluster. So from an external user point of view, he/she would interact with the cluster/server the exactly same as before. Which means the argo api client should work in that case. I don't know the full details of this setup because again I am not an Argo Workflow developer.
I recommend posting the question in https://github.com/argoproj/argo-workflows/issues/3523 for more visibility and tag the Argo Workflow maintainers.
I didn’t see the description of Argo apiserver in your document. If I use this addon, does it mean that the argo api client I am currently using no longer works and I need to change to using k8s native api to create workflows?
The text was updated successfully, but these errors were encountered: