B1: Brainstorm Kubernetes health checks in Canopy - #496
Closed
passcod wants to merge 14 commits into
Closed
Conversation
Upstream landed 'a check name is a category, not an instance': a condition with several instances is one check carrying the instances in its detail, not one check per instance. The K8S spec described the cluster-connection self-alert as one check per registered cluster; reword it as a single Kubernetes cluster connectivity check with each cluster an instance, matching the self-alerts fold and CHK's new 'Checks with instances' rule. 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
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
This PR captures the brainstorm and planning output for bringing Kubernetes-based Tamanu deployments under Canopy's health-check coverage, rather than any implementation of the checks themselves. It adds:
kubernetescheck source, Canopy-determined reachability), and open questions still to resolve.monitoring/kubernetes.md,monitoring/checks.md,self-alerts.md,statuses.md) describing the intended behaviour at a high level for the spawned cards to implement against.draft-card-breakdown,review-testing-notes) used to produce and review this kind of breakdown/plan work, plus the.claude/skillssymlink to expose them.No product code changes are included; this is groundwork for the child cards listed in the breakdown.
Test plan
Docs/planning only — no application behaviour changed, so no functional testing applies. Reviewed the breakdown and plan for internal consistency with the spec updates, and confirmed the new skills follow the existing skill file conventions.