triage out kubernetes (team#40478)

policy/tpa-rfc-56-large-file-storage.md

@@ -197,11 +197,6 @@ Counter examples:
 
 just throwing ideas out there.
 
-in kubernetes, assuming we might want to go there:
-
-  * <https://longhorn.io/> \- k8s volumes, native-only, no legacy support?
-  * <https://rook.io/> \- ceph operator
-
 object storage options:
 
   * [minio][]: suggested/shipped by gitlab omnibus now?
@@ -356,6 +351,22 @@ some storm brewing there.
 [this hacker news discussion]: https://news.ycombinator.com/item?id=32148007
 [licensing dispute]: https://blocksandfiles.com/2023/03/26/we-object-minio-says-no-more-open-license-for-you-weka/
 
+## Kubernetes
+
+In Kubernetes, storage is typically managed by some sort of operator
+that provides volumes to the otherwise stateless "pods" (collections
+of containers). Those, in turn, are then designed to offer large
+storage capacity that automatically scales as well. Here are two
+possible options:
+
+  * <https://longhorn.io/> - Kubernetes volumes, native-only, no legacy support?
+  * <https://rook.io/> - Ceph operator
+
+Those were not evaluated any further. Kubernetes itself is quite a
+beast and seems overkill to fix the immediate problem at hand,
+although it could be interesting to manage our growing fleet of
+containers eventually.
+
 # Costs
 
 # Approval