docs: add Docker mesh observability example#363
Open
SeCuReDmE-main-dev wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
PR: Add Docker mesh observability and sensitive-source isolation example
Linked Issue
Refs #362
Summary
This PR adds a docs-only example for running multiple CodeProject.AI Server containers in a Docker mesh while keeping persistent volumes, private workload networks, and observability boundaries explicit.
The page covers TCP/UDP
32168,KnownMeshHostnames, named volumes, Docker labels, optional metadata-only observability, and sensitive-source logging guidance.Scope
Included:
docs/;Excluded:
Validation
Commands run:
docker compose config --quietEndpoint checks:
Network check:
Known Risks
Reviewer Notes