Update local-testing document to include debugging techniques #7300
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rynowak
reviewed
Mar 14, 2024
|
|
||
|
|
||
| ## Preferred Tools used to visualize k8s logs (pros/cons) | ||
| (@yetkin/@vishwa) |
There was a problem hiding this comment.
I'm a big fan of stern. https://github.com/stern/stern
stern '.*' -n radius-systemoutputs all logs from Radius componentsstern 'ucpd.*' -n radius-systemoutputs UCP logs.
There was a problem hiding this comment.
It would also be nice to have some non-JSON options for log viewing. JSON logs are good for machines and bad for humans
rynowak
reviewed
Mar 14, 2024
| ## Github Pipelines | ||
| (@vinaya, @willsmith) | ||
|
|
||
| ## Container Dev |
There was a problem hiding this comment.
Suggested change
| ## Container Dev | |
| ## Devcontainers |
I'd suggest retitling the section. Devcontainer is a specific technology.
rynowak
reviewed
Mar 14, 2024
|
|
||
| ## Container Dev | ||
| (??) Describe good usecases to debug using dev containers | ||
|
|
There was a problem hiding this comment.
A few usecases I really like for devcontainers
- You don't need to install anything on your machine. If you're doing a few contributions to a repo it's really nice to have an on rails process for contributing without hunting down dependencies.
- If a repo has a devcontainer then it supports codespaces. Codespaces are awesome because you can have multiple of them.
- You can run additional stateful things in a codespace/devcontainer. eg: you can have your codespace launch a Kubernetes cluster and install Radius. Then you can just close VS Code or your browser and it goes away.
This isn't really practical "do this" kind of info, but some of the reasons why devcontainers are useful.
lakshmimsft
had a problem deploying
to
functional-tests
GitHub Actions
Failure
|
This pull request has been automatically marked as stale because it has been inactive for 90 days. Remove stale label or comment or this PR will be closed in 7 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Draft outline document to update local-testing document to include debugging techniques used by team.
Team members tagged in document are requested to update sections and create independent PRs with updates.
Type of change