📚 Documentation Issue Summary
The Kubernetes deployment guide has a Markdown formatting issue in the PostgreSQL ConfigMap example. The closing code fence is not indented inside the Material for MkDocs tab block, so the rendered page shows the bash fence and command text as normal prose instead of a formatted code block.
📍 Location of the Problem
docs/docs/deployment/kubernetes.md, under Configuration via ConfigMap > With PostgreSQL.
✏️ Type of Issue
💡 Suggested Fix or Clarification (optional)
Indent the closing fenced-code marker for the PostgreSQL tab block so it remains inside the tab content.
🧠 Environment (optional)
| Key |
Value |
| Docs version |
main |
| Platform |
macOS |
| Docs build method |
MkDocs / rendered docs page |
🧩 Additional Context (optional)
The local docs build could not be run because docs/.venv/bin/activate is missing in the current checkout.
📚 Documentation Issue Summary
The Kubernetes deployment guide has a Markdown formatting issue in the PostgreSQL ConfigMap example. The closing code fence is not indented inside the Material for MkDocs tab block, so the rendered page shows the bash fence and command text as normal prose instead of a formatted code block.
📍 Location of the Problem
docs/docs/deployment/kubernetes.md, under Configuration via ConfigMap > With PostgreSQL.✏️ Type of Issue
💡 Suggested Fix or Clarification (optional)
Indent the closing fenced-code marker for the PostgreSQL tab block so it remains inside the tab content.
🧠 Environment (optional)
mainmacOSMkDocs / rendered docs page🧩 Additional Context (optional)
The local docs build could not be run because
docs/.venv/bin/activateis missing in the current checkout.