Use `sniHosts` instead of `sni_hosts` in examples (#7178)

* Use `sniHosts` instead of `sni_hosts` in examples

* Trigger netlify

content/en/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/index.md

@@ -418,7 +418,7 @@ to hold the configuration of the NGINX server:
       tls:
       - match:
         - port: 443
-          sni_hosts:
+          sniHosts:
           - nginx.example.com
         route:
         - destination:

content/en/docs/tasks/traffic-management/egress/egress-gateway/index.md

@@ -309,7 +309,7 @@ You need to specify port 443 with protocol `TLS` in a corresponding `ServiceEntr
         - gateways:
           - mesh
           port: 443
-          sni_hosts:
+          sniHosts:
           - edition.cnn.com
         route:
         - destination:
@@ -321,7 +321,7 @@ You need to specify port 443 with protocol `TLS` in a corresponding `ServiceEntr
         - gateways:
           - istio-egressgateway
           port: 443
-          sni_hosts:
+          sniHosts:
           - edition.cnn.com
         route:
         - destination:

content/en/docs/tasks/traffic-management/egress/egress-tls-origination/index.md

@@ -88,7 +88,7 @@ This time, however, use a single `ServiceEntry` to enable both HTTP and HTTPS ac
       tls:
       - match:
         - port: 443
-          sni_hosts:
+          sniHosts:
           - edition.cnn.com
         route:
         - destination:

content/en/docs/tasks/traffic-management/egress/wildcard-egress-hosts/index.md

@@ -61,7 +61,7 @@ only much more convenient when there are many hosts within the common domain.
       tls:
       - match:
         - port: 443
-          sni_hosts:
+          sniHosts:
           - "*.wikipedia.org"
         route:
         - destination:
@@ -153,7 +153,7 @@ the set of domains.
         - gateways:
           - mesh
           port: 443
-          sni_hosts:
+          sniHosts:
           - "*.wikipedia.org"
         route:
         - destination:
@@ -166,7 +166,7 @@ the set of domains.
         - gateways:
           - istio-egressgateway
           port: 443
-          sni_hosts:
+          sniHosts:
           - "*.wikipedia.org"
         route:
         - destination:
@@ -479,7 +479,7 @@ The SNI proxy will forward the traffic to port `443`.
         - gateways:
           - mesh
           port: 443
-          sni_hosts:
+          sniHosts:
           - "*.wikipedia.org"
         route:
         - destination:
@@ -585,7 +585,7 @@ The SNI proxy will forward the traffic to port `443`.
        - gateways:
          - mesh
          port: 443
-         sni_hosts:
+         sniHosts:
          - "*.wikipedia.org"
        route:
        - destination:
@@ -598,7 +598,7 @@ The SNI proxy will forward the traffic to port `443`.
        - gateways:
          - istio-egressgateway-with-sni-proxy
          port: 443
-         sni_hosts:
+         sniHosts:
          - "*.wikipedia.org"
        route:
        - destination:

content/en/docs/tasks/traffic-management/ingress/ingress-sni-passthrough/index.md

@@ -207,7 +207,7 @@ to hold the configuration of the NGINX server:
       tls:
       - match:
         - port: 443
-          sni_hosts:
+          sniHosts:
           - nginx.example.com
         route:
         - destination: