問題文
A platform engineer proposes storing each product team's per-request audit entries as objects of a new custom kind, so that they can be queried with the cluster's command line tool. What does the Kubernetes documentation say about this design?
選択肢
- Avoid it, because storing application, end user or monitoring data in the Kubernetes API typically represents a design that is too closely coupled.
- It is acceptable as long as the number of objects stays small, because the guidance against it is about the load on the cluster's data store rather than about the shape of the design, and a low volume of entries does not create that load.
- It is the recommended approach, since it gives the data the API's authorization model, so the audit entries would inherit the cluster's own access rules for free.
- Use a ConfigMap for each entry instead.