We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Even though it famously "works on my machine":tm:!
PR run succeeds: https://github.com/admiraltyio/multicluster-scheduler/actions/runs/146754445 Merge commit fails: https://github.com/admiraltyio/multicluster-scheduler/actions/runs/147689563 No-op commit succeeds: https://github.com/admiraltyio/multicluster-scheduler/actions/runs/147716838
When it fails, it happens immediately after the Argo workflow starts. I suspect a webhook isn't ready?
I added a kubectl cluster-info dump saved as artifact to better understand what's going on. We should look into it next time the test fails.
kubectl cluster-info dump
The text was updated successfully, but these errors were encountered:
fixed by 57de1e1 (I think)
Sorry, something went wrong.
No branches or pull requests
Even though it famously "works on my machine":tm:!
PR run succeeds: https://github.com/admiraltyio/multicluster-scheduler/actions/runs/146754445
Merge commit fails: https://github.com/admiraltyio/multicluster-scheduler/actions/runs/147689563
No-op commit succeeds: https://github.com/admiraltyio/multicluster-scheduler/actions/runs/147716838
When it fails, it happens immediately after the Argo workflow starts. I suspect a webhook isn't ready?
I added a
kubectl cluster-info dump
saved as artifact to better understand what's going on. We should look into it next time the test fails.The text was updated successfully, but these errors were encountered: