Skip to content

#90 Document Dogu V3 artifacts and their relationships - #91

Open
henry-bobka wants to merge 6 commits into
feature/61540-dogu-v3-multinode-environmentfrom
feature/61403-dogu-v3-artifacts
Open

#90 Document Dogu V3 artifacts and their relationships#91
henry-bobka wants to merge 6 commits into
feature/61540-dogu-v3-multinode-environmentfrom
feature/61403-dogu-v3-artifacts

Conversation

@henry-bobka

@henry-bobka henry-bobka commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Document the core artifacts of a Dogu V3 and how they work together:

  • Explain the Helm chart as the leading Dogu package: Chart.yaml, chart values and schema, companion files, and templates/.
  • Cover the CES integration resources: AuthRegistration, Exposition, service accounts, and Warp Menu.
  • Map how former dogu.json responsibilities are moved or removed (field by field), linking the owning CRDs/APIs rather than implementation.
  • Note the risks of renaming Kubernetes resources (data loss, credential re-issue).

Closes: #90

@henry-bobka
henry-bobka changed the base branch from main to feature/61540-dogu-v3-multinode-environment July 21, 2026 13:13
@henry-bobka
henry-bobka force-pushed the feature/61540-dogu-v3-multinode-environment branch from e383493 to 227eaf7 Compare July 22, 2026 06:47
@henry-bobka
henry-bobka force-pushed the feature/61403-dogu-v3-artifacts branch from 96b6493 to 192697c Compare July 22, 2026 06:48
- Describe artifacts in more detail and link them to the corrensponding docs in the crds
- Delete charts and replace them with tables
- Move specific instructions to best practice
- Remove columns "Owner" and "When needed"
- link to concepts to have a single link hop to the repo
- remove chapter that listed all dogu v2 fields
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants