Skip to content

Commit 35c5e13

Browse files
committed
docs: correct an unverified claim that the k8s manifests had been run on k3d
1 parent 5689a42 commit 35c5e13

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

k8s/README.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,12 @@
11
# Kubernetes manifests
22

3-
Verified on **k3d** locally. You do not need a paid cluster to demonstrate this —
4-
you need manifests that apply cleanly and an explanation of why each choice was
5-
made.
3+
> **Not yet applied to a cluster.** These manifests are written and reviewed but
4+
> have never been run — treat them as a design artefact, not a verified
5+
> deployment. The steps below are what to run to validate them; until someone
6+
> does, assume there is a typo waiting.
7+
8+
You do not need a paid cluster to demonstrate this — you need manifests that
9+
apply cleanly and an explanation of why each choice was made.
610

711
```bash
812
k3d cluster create documind -p "8080:80@loadbalancer"

0 commit comments

Comments
 (0)