Skip to content
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

Closed
soumochak83 opened this issue Apr 23, 2020 · 6 comments
Closed

Comments

@soumochak83
Copy link

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

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
kind/bug 0.66

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@jbottum
Copy link
Contributor

jbottum commented May 5, 2020

@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

@jbottum
Copy link
Contributor

jbottum commented May 12, 2020

@soumochak83 Is this still a valid issue or should we close this ?

@kubeflow-bot kubeflow-bot removed this from To Do in Needs Triage May 12, 2020
@soumochak83
Copy link
Author

soumochak83 commented May 14, 2020 via email

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
area/docs 0.64

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@stale
Copy link

stale bot commented Aug 12, 2020

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.

@stale stale bot closed this as completed Aug 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants