Skip to content

Enhance Istio Ingress explanations #1023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 16 commits into from
Feb 26, 2018
Merged

Enhance Istio Ingress explanations #1023

Changes from all commits
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
b54ddbf
Istio Ingress Controller -> Istio Ingress
vadimeisenbergibm Feb 22, 2018
37cce34
Ingress Resources -> Ingress Resource
vadimeisenbergibm Feb 22, 2018
9ccb7da
clarified Istio Ingress vs. Kubernetes Resource
vadimeisenbergibm Feb 22, 2018
545938b
Istio ingress -> Istio Ingress
vadimeisenbergibm Feb 22, 2018
099173a
Ingress Resource -> Ingress specification
vadimeisenbergibm Feb 23, 2018
db2152b
it allows defining -> it allows one to define
vadimeisenbergibm Feb 23, 2018
1acb007
istio-ingress pod -> istio-ingress service
vadimeisenbergibm Feb 23, 2018
b620b93
rephrased the sentence about applying Istio features
vadimeisenbergibm Feb 23, 2018
1f8ea41
Istio Ingress -> The Istio Ingress
vadimeisenbergibm Feb 23, 2018
dda3dda
The following are the known limitations -> The following are known li…
vadimeisenbergibm Feb 23, 2018
3d8810d
Merge branch 'master' into explain_ingress
vadimeisenbergibm Feb 23, 2018
a45c2b8
Merge branch 'master' into explain_ingress
vadimeisenbergibm Feb 23, 2018
579a7f4
Merge branch 'master' into explain_ingress
vadimeisenbergibm Feb 25, 2018
0b332ac
into-the-cluster traffic -> traffic entering the cluster
vadimeisenbergibm Feb 26, 2018
b68e016
Merge branch 'master' into explain_ingress
vadimeisenbergibm Feb 26, 2018
b9b3b55
second time: into-the-cluster traffic -> traffic entering the cluster
vadimeisenbergibm Feb 26, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 18 additions & 14 deletions _docs/tasks/traffic-management/ingress.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Istio Ingress Controller
overview: Describes how to configure the Istio ingress controller on Kubernetes.
title: Istio Ingress
overview: Describes how to configure Istio Ingress on Kubernetes.

order: 30

Expand All @@ -9,18 +9,22 @@ type: markdown
---

This task describes how to configure Istio to expose a service outside of the service mesh cluster.
In a Kubernetes environment, the [Kubernetes Ingress Resources](https://kubernetes.io/docs/concepts/services-networking/ingress/)
In a Kubernetes environment, the [Kubernetes Ingress Resource](https://kubernetes.io/docs/concepts/services-networking/ingress/)
allows users to specify services that should be exposed outside the
cluster. However, the Ingress Resource specification is very minimal,
allowing users to specify just hosts, paths and their backing services.
The following are the known limitations of Istio ingress:
cluster. It allows one to define a backend service per virtual host and path.

1. Istio supports standard Kubernetes Ingress specification without
annotations. There is no support for `ingress.kubernetes.io` annotations
in the Ingress resource specifications. Any annotation other than
`kubernetes.io/ingress.class: istio` will be ignored.
2. Regular expressions in paths are not supported.
3. Fault injection at the Ingress is not supported.
Once the Istio Ingress specification is defined, the traffic entering the cluster is directed through the `istio-ingress` service. As a result, Istio features, for example, monitoring and route rules, can be applied to the traffic entering the cluster.

The Istio Ingress specification is based on the standard [Kubernetes Ingress Resource](https://kubernetes.io/docs/concepts/services-networking/ingress/) specification, with the following differences:

1. Istio Ingress specification contains `kubernetes.io/ingress.class: istio` annotation.

2. All other annotations are ignored.

The following are known limitations of Istio Ingress:

1. Regular expressions in paths are not supported.
2. Fault injection at the Ingress is not supported.

## Before you begin

Expand All @@ -46,7 +50,7 @@ The following are the known limitations of Istio ingress:

## Configuring ingress (HTTP)

1. Create a basic Ingress Resource for the httpbin service
1. Create a basic Ingress specification for the httpbin service

```bash
cat <<EOF | kubectl create -f -
Expand Down Expand Up @@ -173,7 +177,7 @@ The following are the known limitations of Istio ingress:
kubectl create -n istio-system secret tls istio-ingress-certs --key /tmp/tls.key --cert /tmp/tls.crt
```

1. Create the Ingress Resource for the httpbin service
1. Create the Ingress specification for the httpbin service

```bash
cat <<EOF | kubectl create -f -
Expand Down