-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with executor image and executor runtime - Kubeflow 0.5 on OCP 3.11 #4974
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
@soumochak83 Hi, did you get this resolved. Do you need to run on Kubeflow 0.5. I think you will get more consideration if you could run on Kubeflow 1.x |
@soumochak83 Is this still a valid issue or should we close this ? |
Hi Josh - I was still not able to run workflows in Kubeflow 0.5 on OCP
3.11. Will it run on OCP 4.3? Do you have any reference document to run
workflow on 4.3?
Thanks,
Soumo
…On Wed, May 13, 2020 at 2:42 AM Josh Bottum ***@***.***> wrote:
@soumochak83 <https://github.com/soumochak83> Is this still a valid issue
or should we close this ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4974 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOVLEC5SWMONNKHQCRRELODRRG3UJANCNFSM4MO75LTA>
.
|
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
We are trying some simple Argo based experiments like - Hello World and DAG. We have configured the workflow controller config map to use executor image as Argo 2.7.0 and executor runtime as k8sapi. While running the workflow yaml we see that executor image got changed to 2.7.1 and sometime executor runtime gets changed to docker. This happens randomly and we do not find a good reasoning behind this behavior. Can someone explain?
Also, how can we upgrade workflow controller to v 2.7.4? In kubeflow we have 2.2.0
The text was updated successfully, but these errors were encountered: