문제: infra/ 43개 중 12개는 코드·테스트·workflow·스크립트 어디서도
읽지 않는다(httpclient·jpa·messaging·notification의 toxiproxy compose와
README). nginx 설정, Kubernetes PVC 인증 job, DB 역할 SQL 셋은 운영
인프라라 개발 repo에 둘 것이 아니다(소유자 결정 2026-11-07). release.yml
의 fileserver-pvc-certification job은 그 매니페스트 문자열만 grep했다.
고른 방법:
- 15개를 지운다.
- 운영 조건만 그 기능 문서에 한국어로 남긴다.
docs/fileserver/operations.md 「운영 환경이 지켜야 할 조건」(nginx
internal location·alias·X-Accel-Redirect 헤더 제거·스트리밍, PVC
ReadWriteOnce·fsGroup), storage-certification.md(인증 절차),
docs/jpa/security.md 「역할과 권한」·「서버 설정」(역할 SQL과
jpa/postgres README 내용), docs/messaging/security.md(인증서 SAN).
httpclient TLS README 내용은 docs/httpclient/security.md에 이미 있다.
- release.yml job과 needs 줄, fileserver-pr.yml·pr-adapters.yml의 지운
경로 필터를 지운다.
- fileserver 지원 표의 "Kubernetes ReadWriteOnce PVC — Limited" 행은
근거 job이 없어져 「주장하지 않음」으로 옮긴다.
버린 대안: 인프라 파일을 project-infra로 옮기기(설계 Q6). 그 repo는
특정 프로젝트용이라 범용 템플릿 파일을 받을 자리가 없다.
위험·한계: 지원 표에서 PVC 주장이 빠진다. 파생 서비스가 그 파일을
배포에 썼다면 병합이 지운다(B-50). 클러스터 인증은 이제 배포하는 쪽이
문서 절차로 한다.
검증(desktop, 트리 749a3328, ~/t1-layout-logs/):
- :composition:fileserver-platform:check :app-bootstrap:check
:app-bootstrap:documentContractTest rc=0 (repositoryContractTest,
FileserverDocumentationCoverageTest 실행)
- :verifyStrictLaneStages --dry-run rc=0
- scripts/verify-compose-profile-contracts.sh rc=0 (18 lane)
- check-work-docs.py, 상대 링크 검사 rc=0
Refs: design-docs repo-structure/01-backend-layout.md 4.4, 6.3
BREAKING CHANGE: infra/fileserver/nginx, infra/fileserver/kubernetes, infra/jpa, infra/httpclient, infra/messaging, infra/notification/toxiproxy와 release.yml fileserver-pvc-certification job이 없어진다. docs/upgrade/2026-11-maturity-review.md B-50.
4.0 KiB
Fileserver support matrix
A support level here is a claim about evidence, not about intent. Every row names the CI job that
produces that evidence; FileserverDocumentationCoverageTest fails the build if a row names a job
that does not exist, so a level can never outlive the test that justified it.
Levels
| Level | What it means |
|---|---|
| Stable | Certified on every pull request. Contract changes are breaking changes. |
| Beta | Certified nightly. The contract may still change with a deprecation notice. |
| Limited | Certified on the release gate only, under stated constraints. |
| Compatibility | Accepted but not optimized; known caveats are listed inline. |
| Experimental | Off by default, unratified upstream, may change without notice. |
Runtime profiles
| Profile | Level | CI job |
|---|---|---|
| Local filesystem (ext4) content store | Stable | fileserver-local-ext4-contract |
| Spring MVC transport (raw, multipart, batch, download) | Stable | fileserver-http-contract |
| Path, filename, range, and problem-detail hardening | Stable | fileserver-security-suite |
| Bounded-memory transfer | Stable | fileserver-bounded-memory |
| Application and architecture invariants | Stable | fileserver-unit-and-architecture |
| Runtime assembly (the capability starts with the flag on) | Stable | fileserver-unit-and-architecture |
| tus 1.0 resumable uploads | Stable | fileserver-http-contract |
| Crash-recovery matrix | Beta | fileserver-process-kill-matrix |
| NFSv4 ambiguity handling | Beta | fileserver-nfs-ambiguity |
| Large-file and slow-client performance | Beta | fileserver-large-file-performance |
| Multi-instance writer lease | Beta | fileserver-multi-instance-lease |
Nginx X-Accel-Redirect delegation |
Limited | fileserver-http-contract |
| Telemetry sensitive-data suppression | Stable | fileserver-sensitive-telemetry-scan |
| Documentation and support-claim coverage | Stable | fileserver-documentation-gate |
| Full release verification | Stable | fileserver-full-verification |
| HTTP resumable uploads draft-12 | Experimental | fileserver-http-contract |
WebFlux transport removed
The reactive router and handlers (web.fileserver.reactive) were removed on 2026-09-25 (D4: the
template is servlet on virtual threads). The shipped composition could never select them — the web
leaf puts DispatcherServlet on the classpath, so Boot resolves SERVLET.
Explicitly not claimed
These have no job, and therefore no claim:
-
Kubernetes PVC(ReadWriteOnce 포함). 이 repo는 클러스터 매니페스트와 그것을 검사하던 release job을 2026-11-07에 지웠다. volume이 지켜야 할 조건은 operations.md 「운영 환경이 지켜야 할 조건」, 인증 절차는 storage-certification.md다. 클러스터 결과는 배포하는 쪽이 만든다.
-
Kubernetes ReadWriteMany PVC. Concurrent writers across nodes are not certified.
-
Windows NTFS as a production storage root. The filename policy strips the characters NTFS reserves, but no job certifies the publish path there.
-
Object storage as a content store. The contract exists (
ContentStoreContract) but no adapter implements it yet. -
Server-side malware scanning. The verification pipeline has the port and the verdict precedence; no scanner is shipped.
Where the rest is written down
- configuration.md — every
app.fileserver-platform.*key, its default, and the conditions that fail startup rather than degrade. - design-deviations.md — where the implementation departs from the frozen design, why, and the test that pins each decision.
- http-contract.md — the wire contract.
- security.md — the threat model and what enforces each control.
- operations.md — runbooks, each starting from a metric.
- storage-certification.md — how a volume is certified.
- upgrade-guide.md — what changes between versions.