If you want to use a custom nginx.conf on Google Kubernetes Engine, prepare one by
extending this
sample nginx.conf.
Here is a snippet of the configuration required by Cloud Endpoints:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-02 UTC."],[[["Using a custom nginx configuration with the `-n` flag is generally not recommended as it can disrupt the intended functionality of ESP."],["The preferred method to customize the nginx configuration involves deploying an ESP container, copying the generated config, and modifying the copy, repeating this process for new ESP versions or flag changes."],["To utilize a custom `nginx.conf` on Google Kubernetes Engine, one should extend the provided sample configuration and include specific Cloud Endpoints configurations in it, such as including `/etc/nginx/mime.types` and utilizing the endpoints feature with relevant fields."],["After creating a custom `nginx.conf`, you can deploy it to Kubernetes by creating a ConfigMap and then updating your Kubernetes configuration to reference the custom nginx configuration."]]],[]]