luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Use nested tabs for gateway examples

This commit is contained in:
Luke Kysow 2021-01-06 16:45:35 -08:00
parent 92415d9c0c
commit 0a7d2d0ff9
No known key found for this signature in database
GPG Key ID: FA168D4DC3F04307
2 changed files with 120 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
website/content/docs/agent/config-entries/ingress-gateway.mdx
View File

@ -50,6 +50,8 @@ A wildcard specifier cannot be set on a listener of protocol `tcp`.
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
Set up a TCP listener on an ingress gateway named "us-east-ingress" to proxy traffic to the "db" service:
@ -71,7 +73,7 @@ Listeners = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a TCP listener on an ingress gateway named "us-east-ingress" in the default namespace
to proxy traffic to the "db" service in the ops namespace:
@ -95,8 +97,12 @@ Listeners = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
Set up a TCP listener on an ingress gateway named "us-east-ingress" to proxy traffic to the "db" service:
@ -114,7 +120,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a TCP listener on an ingress gateway named "us-east-ingress" in the default namespace
to proxy traffic to the "db" service in the ops namespace:
@ -134,8 +140,12 @@ spec:
namespace: ops
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
Set up a TCP listener on an ingress gateway named "us-east-ingress" to proxy traffic to the "db" service:
@ -158,7 +168,7 @@ Set up a TCP listener on an ingress gateway named "us-east-ingress" to proxy tra
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a TCP listener on an ingress gateway named "us-east-ingress" in the default namespace
to proxy traffic to the "db" service in the ops namespace:
@ -183,6 +193,8 @@ to proxy traffic to the "db" service in the ops namespace:
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>
@ -190,6 +202,8 @@ to proxy traffic to the "db" service in the ops namespace:
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
Set up a wildcard HTTP listener on an ingress gateway named "us-east-ingress" to proxy traffic to all services in the datacenter.
Also make two services available over a custom port with user-provided hosts, and enable TLS on every listener:
@ -230,7 +244,7 @@ Listeners = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a wildcard HTTP listener on an ingress gateway named "us-east-ingress" to proxy traffic to all services in the frontend namespace.
Also make two services in the frontend namespace available over a custom port with user-provided hosts, and enable TLS on every listener:
@ -274,8 +288,12 @@ Listeners = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
Set up a wildcard HTTP listener on an ingress gateway named "us-east-ingress" to proxy traffic to all services in the datacenter.
Also make two services available over a custom port with user-provided hosts, and enable TLS on every listener:
@ -303,7 +321,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a wildcard HTTP listener on an ingress gateway named "us-east-ingress" to proxy traffic to all services in the frontend namespace.
Also make two services in the frontend namespace available over a custom port with user-provided hosts, and enable TLS on every listener:
@ -334,8 +352,12 @@ spec:
hosts: ['website.example.com', 'website.example.com:4567']
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
Set up a wildcard HTTP listener on an ingress gateway named "us-east-ingress" to proxy traffic to all services in the datacenter.
Also make two services available over a custom port with user-provided hosts, and enable TLS on every listener:
@ -376,7 +398,7 @@ Also make two services available over a custom port with user-provided hosts, an
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a wildcard HTTP listener on an ingress gateway named "us-east-ingress" to proxy traffic to all services in the frontend namespace.
Also make two services in the frontend namespace available over a custom port with user-provided hosts, and enable TLS on every listener:
@ -420,6 +442,8 @@ Also make two services in the frontend namespace available over a custom port wi
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>
@ -427,6 +451,8 @@ Also make two services in the frontend namespace available over a custom port wi
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
Set up a HTTP listener on an ingress gateway named "us-east-ingress" to proxy
traffic to a virtual service named "api".
@ -449,7 +475,7 @@ Listeners = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a HTTP listener on an ingress gateway named "us-east-ingress" in the
default namespace to proxy traffic to a virtual service named "api".
@ -473,8 +499,12 @@ Listeners = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
Set up a HTTP listener on an ingress gateway named "us-east-ingress" to proxy
traffic to a virtual service named "api".
@ -493,7 +523,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a HTTP listener on an ingress gateway named "us-east-ingress" in the
default namespace to proxy traffic to a virtual service named "api".
@ -513,8 +543,12 @@ spec:
namespace: frontend
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
Set up a HTTP listener on an ingress gateway named "us-east-ingress" to proxy
traffic to a virtual service named "api".
@ -538,7 +572,7 @@ traffic to a virtual service named "api".
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Set up a HTTP listener on an ingress gateway named "us-east-ingress" in the
default namespace to proxy traffic to a virtual service named "api".
@ -563,6 +597,8 @@ default namespace to proxy traffic to a virtual service named "api".
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>
@ -573,6 +609,8 @@ backend services:
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
```hcl
Kind = "service-router"
@ -604,7 +642,7 @@ Routes = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
```hcl
Kind = "service-router"
@ -638,8 +676,12 @@ Routes = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
```yaml
apiVersion: consul.hashicorp.com/v1alpha1
@ -661,7 +703,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
```yaml
apiVersion: consul.hashicorp.com/v1alpha1
@ -685,8 +727,12 @@ spec:
namespace: frontend
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
```json
{
@ -718,7 +764,7 @@ spec:
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
```json
{
@ -752,6 +798,8 @@ spec:
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>

72
website/content/docs/agent/config-entries/terminating-gateway.mdx
View File

@ -47,6 +47,8 @@ traffic from the mesh to those services will be evenly load-balanced between the
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the billing service:
@ -62,7 +64,7 @@ Services = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the billing service in the finance namespace:
@ -79,8 +81,12 @@ Services = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the billing service:
@ -95,7 +101,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the billing service in the finance namespace:
@ -110,8 +116,12 @@ spec:
namespace: finance
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the billing service:
@ -128,7 +138,7 @@ Link gateway named "us-west-gateway" with the billing service:
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the billing service in the finance namespace:
@ -146,11 +156,15 @@ Link gateway named "us-west-gateway" in the default namespace with the billing s
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the billing service and specify a CA file for one-way TLS authentication:
@ -167,7 +181,7 @@ Services = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the billing service in the finance namespace,
and specify a CA file for one-way TLS authentication:
@ -186,8 +200,12 @@ Services = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the billing service and specify a CA file for one-way TLS authentication:
@ -203,7 +221,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the billing service in the finance namespace,
and specify a CA file for one-way TLS authentication:
@ -220,8 +238,12 @@ spec:
caFile: /etc/certs/ca-chain.cert.pem
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the billing service and specify a CA file for one-way TLS authentication:
@ -239,7 +261,7 @@ Link gateway named "us-west-gateway" with the billing service and specify a CA f
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the billing service in the finance namespace,
and specify a CA file for one-way TLS authentication:
@ -259,11 +281,15 @@ and specify a CA file for one-way TLS authentication:
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the payments service and specify a CA file, key file, and cert file for mutual TLS authentication:
@ -282,7 +308,7 @@ Services = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the payments service in the finance namespace.
Also specify a CA file, key file, and cert file for mutual TLS authentication:
@ -303,8 +329,12 @@ Services = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the payments service and specify a CA file, key file, and cert file for mutual TLS authentication:
@ -322,7 +352,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the payments service in the finance namespace.
Also specify a CA file, key file, and cert file for mutual TLS authentication:
@ -341,8 +371,12 @@ spec:
certFile: /etc/certs/gateway.cert.pem
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with the payments service and specify a CA file, key file, and cert file for mutual TLS authentication:
@ -362,7 +396,7 @@ Link gateway named "us-west-gateway" with the payments service and specify a CA
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with the payments service in the finance namespace.
Also specify a CA file, key file, and cert file for mutual TLS authentication:
@ -384,11 +418,15 @@ Also specify a CA file, key file, and cert file for mutual TLS authentication:
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>
<Tabs>
<Tab heading="HCL">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with all services in the datacenter, and configure default certificates for mutual TLS.
Also override the SNI and CA file used for connections to the billing service:
@ -413,7 +451,7 @@ Services = [
```
</Tab>
<Tab heading="HCL (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with all services in the finance namespace,
and configure default certificates for mutual TLS. Also override the SNI and CA file used for connections to the billing service:
@ -440,8 +478,12 @@ Services = [
]
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Kubernetes YAML">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with all services in the datacenter, and configure default certificates for mutual TLS.
Also override the SNI and CA file used for connections to the billing service:
@ -463,7 +505,7 @@ spec:
```
</Tab>
<Tab heading="Kubernetes YAML (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with all services in the finance namespace,
and configure default certificates for mutual TLS. Also override the SNI and CA file used for connections to the billing service:
@ -486,8 +528,12 @@ spec:
sni: billing.service.com
```
</Tab>
</Tabs>
</Tab>
<Tab heading="JSON">
<Tabs>
<Tab heading="Consul OSS">
Link gateway named "us-west-gateway" with all services in the datacenter, and configure default certificates for mutual TLS.
Also override the SNI and CA file used for connections to the billing service:
@ -514,7 +560,7 @@ Also override the SNI and CA file used for connections to the billing service:
```
</Tab>
<Tab heading="JSON (Consul Enterprise)">
<Tab heading="Consul Enterprise">
Link gateway named "us-west-gateway" in the default namespace with all services in the finance namespace,
and configure default certificates for mutual TLS. Also override the SNI and CA file used for connections to the billing service:
@ -543,6 +589,8 @@ and configure default certificates for mutual TLS. Also override the SNI and CA
}
```
</Tab>
</Tabs>
</Tab>
</Tabs>