It will allow to: 1. serve the assets directly 2. cache the responses The `image:` should point to the official nginx docker image The nginx config can be generated as a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/): - see https://github.com/huggingface/gitaly-internals/blob/main/kube/gitaly/templates/gitaly/config.yaml - [mounted](https://github.com/huggingface/gitaly-internals/blob/d7e20a22bac939c1ab49d1a15e5523d2b3015cdd/kube/gitaly/templates/gitaly/statefulset.yaml#L106-L108) as a [volume](https://github.com/huggingface/gitaly-internals/blob/d7e20a22bac939c1ab49d1a15e5523d2b3015cdd/kube/gitaly/templates/gitaly/statefulset.yaml#L124-L128) - see https://github.com/huggingface/datasets-server/blob/af9a93d4b810c2353de01369ad49f2065272af85/services/api/INSTALL.md for the content of the config (cache + assets/)
It will allow to:
The
image:should point to the official nginx docker imageThe nginx config can be generated as a ConfigMap: