Unverified Commit b9ebc872 authored by Lemon-miaow's avatar Lemon-miaow
Browse files

docs(troubleshooting): the [INERT] legend points at a field that no longer exists 

The legend said "§12 lists the one field this still applies to", but the last
inert field (spec.storage.retainOnDelete) was removed rather than implemented
(§13), and §12 has said "every field below is read by a controller" since.
Reworded so a reader whose change looks ignored follows the condition question
instead of hunting for a dead field.
parent c57daaf8

docs/troubleshooting.md

+5 −2
Changes for docs/troubleshooting.md: 5 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -20,8 +20,11 @@ graded for how far the in-repo Go test suite proves the behaviour: 
  containerd, Postgres, or the network, not by Felis Go code; you will see it in

  `kubectl describe` / pod logs, never in `MinecraftServer.status`.

- **[INERT]** — the configuration field exists in the CRD but no controller

  reads it. Tuning it does nothing. §12 lists the one field this still applies

  to, alongside the fields that *are* read and the condition each depends on.

  reads it. Tuning it does nothing. **No CRD field carries this status today**;

  the last one, `spec.storage.retainOnDelete`, was removed rather than

  implemented (§13 records why). A field whose change seems ignored is almost

  always a condition instead — §12 lists the fields that *are* read and the

  condition each depends on.



The operator never invents the parent domain; routing identity is

`spec.subdomain` under the deployment zone. Examples below use