Se você quiser usar um nginx.conf personalizado no Google Kubernetes Engine, prepare um estendendo esta amostra nginx.conf. Aqui está um snippet de configuração exigido pelo Cloud Endpoints:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 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."]]],[]]