You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2023/01/04 11:09:30 UTC

[GitHub] [skywalking] kezhenxu94 commented on issue #10228: [Feature] [Infra-e2e] Support debugging on an existing kubernetes cluster and single-step debugging

kezhenxu94 commented on issue #10228:
URL: https://github.com/apache/skywalking/issues/10228#issuecomment-1370788917

   Looks like the proposal is all about setup phase, correct me if I'm wrong, I assumed the users' steps to set up new tests is:
   
   - start a kubernetes cluster
   - run commands to set up the environment 
   - verify the environment is correctly set up
   - compose a kind.yaml file and use it in e2e.yaml to spin up a kubernetes cluster
   - copy the commands in step 2 to e2e.yaml file
   
   I don't recommend start directly from e2e.yaml and debug there, I recommend starting in a local cluster and run the commands locally, after verifications then move those commands into e2e. 
   
   And I assumed if users run those command in a local cluster it should be the same to copy them into the e2e.yaml file. 


-- 
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: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org