doc(kubernetes): J1: map the Tamanu namespace layout Canopy's checks need - #497
Open
passcod wants to merge 1 commit into
Open
doc(kubernetes): J1: map the Tamanu namespace layout Canopy's checks need#497passcod wants to merge 1 commit into
passcod wants to merge 1 commit into
Conversation
Research spike output: required-inputs list mapped onto real resource names, labels, and CNPG conventions in a Tamanu namespace, sourced from the ops tamanu/on-k8s Pulumi stack. Reference for L1/M1/N1. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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
Research spike: adds
.workhorse/plans/j1/plan.md, mapping where every input Canopy's Kubernetes checks and setup need actually lives inside a Tamanu namespace. It's a documentation-only change (one new markdown file) — no application code is touched.The plan covers, per namespace:
facility-<N>resource prefix vs. the facility's actual id/host, and how to join the two) for the server-identity pickerCluster.spec.storage.sizeused for the storage check<prefix>-db-app) used for the DB harvestIt closes with a cross-check table tying these inputs back to the checks in the K8S monitoring spec, and a list of caveats/open items (positional facility prefixes, zero-replica duties being valid, Gateway-vs-Ingress migration, TTL hibernation, and the RBAC read set this implies) for the L1/M1/N1 implementation cards that follow.
Test plan
Documentation-only change; no code or behaviour to test. Reviewed for accuracy against the
tamanu/on-k8sPulumi stack source,ghaCdHelpers.mjs, and the ops k8s specs it cites.