You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apply -enable-snippets cli arg to Ingresses (#2124)
* Apply -enable-snippets cli arg to Ingresses
* Update docs
* add snippet flag python tests
* removing snippets check as we rely on validation
* removing used param
Co-authored-by: Sean O'Neill <[email protected]>
`The namespace/name of the GlobalConfiguration resource for global configuration of the Ingress Controller. Requires -enable-custom-resources. Format: <namespace>/<name>`)
`controller.globalConfiguration.spec` | The spec of the GlobalConfiguration for defining the global configuration parameters of the Ingress Controller. | {}
184
-
`controller.enableSnippets` | Enable custom NGINX configuration snippets in VirtualServer, VirtualServerRoute and TransportServer resources. | false
184
+
`controller.enableSnippets` | Enable custom NGINX configuration snippets in Ingress, VirtualServer, VirtualServerRoute and TransportServer resources. | false
185
185
`controller.healthStatus` | Add a location "/nginx-health" to the default server. The location responds with the 200 status code for any request. Useful for external health-checking of the Ingress controller. | false
186
186
`controller.healthStatusURI` | Sets the URI of health status location in the default server. Requires `controller.healthStatus`. | "/nginx-health"
187
187
`controller.nginxStatus.enable` | Enable the NGINX stub_status, or the NGINX Plus API. | true
Copy file name to clipboardExpand all lines: docs-web/configuration/ingress-resources/advanced-configuration-with-snippets.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,7 @@ server {
68
68
## Summary of Snippets
69
69
70
70
See the [snippets annotations](/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/#snippets-and-custom-templates) documentation for more information.
71
+
However, because of the disadvantages described below, snippets are disabled by default. To use snippets, set the [`enable-snippets`](/nginx-ingress-controller/configuration/global-configuration/command-line-arguments#cmdoption-enable-snippets) command-line argument.
Copy file name to clipboardExpand all lines: docs-web/installation/installation-with-helm.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -252,7 +252,7 @@ The following tables lists the configurable parameters of the NGINX Ingress cont
252
252
- The spec of the GlobalConfiguration for defining the global configuration parameters of the Ingress Controller.
253
253
- {}
254
254
* - ``controller.enableSnippets``
255
-
- Enable custom NGINX configuration snippets in VirtualServer, VirtualServerRoute and TransportServer resources.
255
+
- Enable custom NGINX configuration snippets in Ingress, VirtualServer, VirtualServerRoute and TransportServer resources.
256
256
- false
257
257
* - ``controller.healthStatus``
258
258
- Add a location "/nginx-health" to the default server. The location responds with the 200 status code for any request. Useful for external health-checking of the Ingress controller.
Copy file name to clipboardExpand all lines: docs-web/third-party-modules/opentracing.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ The Ingress Controller supports [OpenTracing](https://opentracing.io/) with the
4
4
5
5
This document explains how to use OpenTracing with the Ingress Controller.
6
6
7
+
**Note**: The examples below use the snippets annotations, which are disabled by default. To use snippets, set the [`enable-snippets`](/nginx-ingress-controller/configuration/global-configuration/command-line-arguments#cmdoption-enable-snippets) command-line argument.
8
+
7
9
## Prerequisites
8
10
1.**Use the Ingress Controller image with OpenTracing.** The default Ingress Controller images don’t include the OpenTracing module. To use OpenTracing, you need to build the image with that module. Follow the build instructions to build the image using `openshift-image` for NGINX or `openshift-image-plus` for NGINX Plus.
9
11
By default, the Dockerfiles install Jaeger as a tracer. However, it is possible to replace Jaeger with other supported [tracers](https://github.com/opentracing-contrib/nginx-opentracing#building-from-source). For that, please modify the Dockerfile accordingly:
0 commit comments