fix(kiali): Verify CI setup for gevals suite kiali#831
fix(kiali): Verify CI setup for gevals suite kiali#831aljesusg wants to merge 2 commits intocontainers:mainfrom
Conversation
| kubectl apply -f dev/config/istio/kiali.yaml -n istio-system | ||
| kubectl wait --namespace istio-system --for=condition=available deployment/kiali --timeout=300s | ||
| kubectl wait --namespace istio-system --for=condition=available deployment/prometheus --timeout=300s | ||
| kubectl wait --for=condition=Ready pod --all -n istio-system --timeout=300s |
There was a problem hiding this comment.
I guess related to the discussion in here? #816
aljesusg
force-pushed
the
fix_ci_for_kiali
branch
from
e435884 to
e9fffd7
Compare
Signed-off-by: Alberto Gutierrez <aljesusg@gmail.com>
aljesusg
force-pushed
the
fix_ci_for_kiali
branch
from
e9fffd7 to
4001e07
Compare
|
/run-mcpchecker kiali |
|
I am working in more issues that I found... we should test this with kiali changes... we didn't expect this sorry. I'll ping you to trigger again the mcpchecker |
aljesusg
force-pushed
the
fix_ci_for_kiali
branch
2 times, most recently
from
77a0443 to
e81285a
Compare
|
It should work now === Overall Statistics === === Statistics by Difficulty === easy: medium: |
|
/run-mcpchecker kiali |
Signed-off-by: Alberto Gutierrez <aljesusg@gmail.com>
aljesusg
force-pushed
the
fix_ci_for_kiali
branch
from
a5a270f to
b1bca07
Compare
aljesusg
changed the title
|
@aljesusg I think we are still having issues in CI, I'm seeing this error most recently: |
|
Yes I pushed with a fix...hardcoding the value in the Makefile...I don't know why the CI id not passing the value |
3 participants
This is the change to verify that all is ok to run gevals for suite kiali.
This should be fixed now.
I created an mcp-config folder to handle additional toolsets configuration. Since each tool has its own configuration under [toolsets.], loading all of them won't cause issues; a tool only runs if it is explicitly enabled.
cc @Cali0707