-
Notifications
You must be signed in to change notification settings - Fork 22
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
The application deployed is not reachable to Meshery #27
Comments
@leecalcote Please assign this to me, I'll raise a PR to fix it, thanks. |
@gyohuangxin excellent. 😄 |
@gyohuangxin This is also an issue for deploying Linkerd and an application on top of it. Another area we can expand on is to have the sample application configurable as different sample applications can act as representative workloads. For a single test comparison, we can run tests on different service meshes with the same sample application. |
@navendu-pottekkat Thanks, I will have a look on this issue. And I aggress with you about extending a configuration of sample applications. We can create an issue on this, which repo is suitable, SMP or here? |
@navendu-pottekkat It failed when executing command
I found that after your PR meshery/meshery#4710 merged, |
@gyohuangxin Yes, we need to pass in a profile name when we are using a test configuration file as well. The test configuration currently does not capture the profile name. Prior to meshery/meshery#4710, the logic was to use the test name as the profile name. This could work well in most use cases but for the action, it would be difficult to automatically collect and organise the test results. To use this change in mesheryctl, the meshery-smp-action was updated as well to fix this error of not having a The Istio benchmark tests does work with Fortio load generator but there seems to be some issue in upstream for wrk2 which is throwing errors (meshery/meshery#4199). The Linkerd tests however does not work. And we need to look into debugging this and fixing this as well as another failure when trying to deploy OSM. Will open up a new issue and link it here for adding the sample application to the job matrix. |
@navendu-pottekkat Thanks, got it. I'll raise a PR to fix Linkerd issue and add some check for profile name. |
@gyohuangxin Great! Thank you 🚀 |
In the process of deploying application on Linkerd, there are some errors when excuting
@navendu-pottekkat Do you or others know about it? |
The script follows this: https://linkerd.io/2.10/getting-started/ I am not sure about the error 🤔 |
I tried it on my own minikube cluster and it works, it's a strange behavior. 🤔 |
@navendu-pottekkat I found the cause of this issue: We should execute |
@gyohuangxin Hmm, does |
@navendu-pottekkat Yes, I tried this in this action:https://github.com/gyohuangxin/meshery-smp-action/runs/4561946823 |
@Revolyssup Do you have any idea why this might happen here? |
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. |
@gyohuangxin Is this still an issue? |
@navendu-pottekkat Yes, as I mentioned, I tried many ways to make Linkerd's application reachable, but it still failed. It's probably a issue of Github's runner, and we are trying to run SMP actions on CNCF cluster, and I will track if this issue will still occurs. |
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. |
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. |
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
Description
The application deployed by SMP github action is not reachable to Meshery.
Expected Behavior
Root cause:
minikube tunnel
is easy to be killed.Screenshots/Logs
Environment:
The text was updated successfully, but these errors were encountered: