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
We currently import the argo client directly, which brings in a large and awkward depedency and means we limit kube-ci to handling argo resource of one specific known version.
In reality we make quite simple updates to argo resources, adding a few parameters, and updating the name. These could be done with simpler yaml manipulation, and then submitted to kube with the dynamic client. This would drop the argo dependency and remove the direct coupling to a specific argo version.
The text was updated successfully, but these errors were encountered:
We currently import the argo client directly, which brings in a large and awkward depedency and means we limit kube-ci to handling argo resource of one specific known version.
In reality we make quite simple updates to argo resources, adding a few parameters, and updating the name. These could be done with simpler yaml manipulation, and then submitted to kube with the dynamic client. This would drop the argo dependency and remove the direct coupling to a specific argo version.
The text was updated successfully, but these errors were encountered: