Skip to content

docs: mark datamesh-python as source of truth for shared service code; add minikube on-ramp note #25

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.

Sign up for GitHub

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

Merged
patterncatalyst merged 1 commit into from
Nov 1, 2026
Merged

docs: mark datamesh-python as source of truth for shared service code; add minikube on-ramp note #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,6 +145,11 @@ The parent repo's tutorial (§1–§16) remains the canonical Minikube-on-Fedora
guide; this repo is the data-mesh reference broken out for its own audience.
The fork was made as of r28 of the parent (June 2026).

This repo is the **source of truth for the shared data-mesh service code**.
Fixes to the services land here first; the §17 capstone in the parent is a
teaching snapshot that may lag. Backport changes from here to the parent, not
the other way around.

## License

This project is dual-licensed to separate the code from the writing:
Expand Down
5 changes: 5 additions & 0 deletions _docs/00-index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,11 @@ By the end of this chapter you can:

## Why this matters

> **Coming from the minikube on Fedora tutorial?** You have already built this
> system: it is the §17 capstone of that tutorial. This reference takes the same
> running mesh further, with the data-architecture background, a deeper look at
> governance and the self-serve platform, and an OpenShift Local path.

Chapter 2 names Dehghani's four principles. Chapter 3 takes the same four and maps each one
to a Kubernetes primitive: namespaces, operators, RBAC. That's the shape of this whole
set. A concept gets introduced, then you watch it land in a running piece of the
Expand Down
Loading