-
Notifications
You must be signed in to change notification settings - Fork 5.3k
doc: update e2e-tests.md to clarify steps running delve locally without GCE #8535
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
base: master
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ylink-lfs The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the e2e testing documentation to clarify how to run delve debugger locally without requiring Google Cloud Engine (GCE) setup. The documentation now explicitly shows how to use conformance test mode to bypass GCE infrastructure requirements.
- Added
KUBERNETES_CONFORMANCE_TEST=yenvironment variable to enable local debugging without GCE - Updated example output to reflect conformance test mode instead of GCE setup
- Added instructions for connecting to the delve debugger from a separate terminal
- Clarified that the default delve port is 2345 and can be customized with
DELVE_PORT
|
/hold |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Which issue(s) this PR fixes:
Coworking with PR ci: allow devs using delve to debug e2e locally without gce #133253