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
Copy file name to clipboardExpand all lines: docs/workloads/application/explanations/expose.md
+13-2
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,11 @@ What good is an application if no one can reach it?
9
9
NAIS tries to make it easy to expose your application to the correct audience.
10
10
Your audience may be other applications within the same [environment](../../explanations/environment.md), or it may be humans or machines on the outside.
11
11
12
+
For each audience, there are different ways to expose your application:
13
+
14
+
-[Service discovery](#service-discovery) for applications within the same environment.
15
+
-[Ingress](#ingress) for users and applications outside the environment.
16
+
12
17
## Service discovery
13
18
14
19
If your audience is other applications within the same environment, they can communicate with your application directly by using _service discovery_.
@@ -42,19 +47,25 @@ Compared to [ingresses](#ingress), using service discovery has several advantage
42
47
43
48
If your audiences consist of human users or other services outside the environment, you will have to expose your application by using an _ingress_.
44
49
50
+
```yaml
51
+
spec:
52
+
ingresses:
53
+
- https://myapplication.example.com
54
+
```
55
+
45
56
An ingress exposes a route for inbound traffic from outside the environment to your application.
46
57
The domain of the URL controls which users and environments that your application is reachable from.
47
58
48
59
Your application may specify multiple ingresses, each using the same or different domains.
49
60
50
-
Ingresses may also include paths.
61
+
Ingresses may also include a trailing path.
51
62
This allows for routing traffic to only specific parts of your application, or as part of a shared domain between multiple applications.
52
63
53
64
:dart: Learn how to [expose your application with an ingress](../how-to/expose.md).
54
65
55
66
:books: See the [ingress reference](../reference/ingress.md) for technical details and options.
56
67
57
-
## Ingress redirects
68
+
### Ingress redirects
58
69
59
70
In some cases, you may want to redirect traffic from one domain to another.
60
71
This can be useful if you have changed the domain of your application, or if you want to redirect users from an old domain to a new one.
This is the reference documentation for [ingresses](../explanations/expose.md#ingress) in NAIS.
7
+
This is the reference documentation for [ingresses](../explanations/expose.md#ingress) in Nais.
8
8
9
9
Ingress is the only way to expose your application to the outside world, this is not the recommended way to communicate between applications running in the same environment. For that, you should use [service discovery](../explanations/expose.md#service-discovery).
10
10
@@ -149,13 +149,16 @@ Percentage of `5xx` errors to the `myapp` application as a ratio of total reques
149
149
)
150
150
```
151
151
152
-
{% if tenant() == "nav" %}
153
-
154
152
## Ingress access logs
155
153
156
-
Request access logs from nginx ingress controller are automatically collected and stored in Kibana.
154
+
Ingress access logs are enabled by default for all applications and accessible from [Grafana Log Explorer](https://grafana.<<tenant()>>.cloud.nais.io/a/grafana-lokiexplore-app/explore) by selecting the `nais-ingress` service.
155
+
156
+
From there you can use the Filter tab to search for logs from your application by using the `ingress_namespace`, `ingress_name` and `url_domain` labels.
157
+
158
+
{% if tenant() == "nav" %}
157
159
158
-
Here are pre-configured queries for the controller logs in the following clusters:
160
+
Ingress logs for on-premise applications are available in Kibana.
161
+
Here are pre-configured queries for ingress logs in the different environments:
0 commit comments