dashanji commented on a change in pull request #64:
URL: 
https://github.com/apache/skywalking-infra-e2e/pull/64#discussion_r741088846



##########
File path: docs/en/setup/Configuration-File.md
##########
@@ -150,6 +152,12 @@ trigger:
 
 The Trigger executed successfully at least once, after success, the next stage 
could be continued. Otherwise, there is an error and exit.
 
+If you get the following error message when using the trigger, You should 
check whether the port is useful. A possible reason may be that the exporting 
service needs time to set up, so you can add a larger interval to avoid the 
error.

Review comment:
       Yes, the resouce is ready before port-forward, I can use curl to get 
data.

##########
File path: docs/en/setup/Configuration-File.md
##########
@@ -53,6 +53,8 @@ The `KinD` environment follow these steps:
 1. Wait until all steps are finished and all services are ready with the 
timeout(second).
 1. Expose all resource ports for host access.
 
+Notice, when you create resources such as webhooks, they need time to set up. 
If you get some error, you can try `sleep` to wait for the resources 
established. 

Review comment:
       I haven't found it yet.

##########
File path: docs/en/setup/Configuration-File.md
##########
@@ -150,6 +152,12 @@ trigger:
 
 The Trigger executed successfully at least once, after success, the next stage 
could be continued. Otherwise, there is an error and exit.
 
+If you get the following error message when using the trigger, You should 
check whether the port is useful. A possible reason may be that the exporting 
service needs time to set up, so you can add a larger interval to avoid the 
error.

Review comment:
       Yes, the resouce is ready before port-forward, I can use `curl` to get 
data.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to