-
Notifications
You must be signed in to change notification settings - Fork 448
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
CI seems to be running on somewhere else than $CLUSTER_NAME #359
Comments
Just using the default namespace and also modifing run-test.sh seems to be the way to go. |
@richardsliu @jlewi do you have any ideas? |
It is probably running under the kubeflow-testing cluster. I will look at your fix. |
@richardsliu As I wrote in a comment in #360 , I'm having trouble getting a working kubeconfig. |
test/scripts/unit-test.sh creates a mysql pod for testing. During #352 it was found to contain some older DB schema, resulting a failed unit test.
I created #357 to investigate the issue. As I changed the kubeconfig set up script to just use "gcloud container clusters get-credentials ${CLUSTER_NAME}", I got this error
I think the mysql pod used to run on the cluster where argo ran.
The text was updated successfully, but these errors were encountered: