ofilter/Istio_Examples
1
0
Fork 0
Code Issues 26 Pull Requests Packages Projects 1 Releases Wiki Activity

Minor update to the global README.md file.

Browse Source
This commit is contained in:
savagebidoof 2023-10-14 10:27:11 +02:00
parent fd3f9b6e95
commit 84b71d9751
1 changed files with 39 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
README.md
View File

@ -8,43 +8,6 @@ Refer to the specific `README.md` in each example for more information, some doc
Currently, the resources are under a relocation and the folders might contain things that don't _really match the topic_.
# Glossary
https://istio.io/latest/docs/reference/glossary/
## Services port names
Istio allows to specify which protocol will run through a port.
It requires the name of the port to be set to a specific format `name: <protocol>(-<suffix>)`.
Starting from Kubernetes 1.18, it also can be specified through the `appProtocol` field in the port, resulting in `appProtocol: <protocol>`.
This means that port names should respect this format to avoid issues, and for such be cautious when setting up the name of the ports.
This applies to multiple Istio elements, but as well to `kind: Services` from default Kubernetes.
For more information about this behavior, refer to:
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection
# Links of interest
- https://istio.io/latest/docs/
- https://istiobyexample.dev/
- https://www.istioworkshop.io/
- https://istio.io/latest/news/
- https://istio.io/latest/blog/
- https://istio.io/latest/about/ecosystem/
# Tree of folders
```text
@ -75,6 +38,9 @@ https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selec
├── 05-Sidecar
│   ├── 01-ingress-proxy-forwarding
│   └── 02-egress-proxy
├── 06-Envoy
│   ├── 01-Envoy-add-response-headers
│   └── 02-envoy-logging
├── 08-AuthorizationPolicy
│   ├── 01-target-namespaces
│   ├── 02-target-service-accounts
@ -96,4 +62,39 @@ https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selec
│   └── Istio-Ingress
└── 99-resources
└── HTTPS-NGINX-DOCKERFILE
```
```
# Glossary
https://istio.io/latest/docs/reference/glossary/
## Services port names
Istio allows to specify which protocol will run through a port.
It requires the name of the port to be set to a specific format `name: <protocol>(-<suffix>)`.
Starting from Kubernetes 1.18, it also can be specified through the `appProtocol` field in the port, resulting in `appProtocol: <protocol>`.
This means that port names should respect this format to avoid issues, and for such be cautious when setting up the name of the ports.
This applies to multiple Istio elements, but as well to `kind: Services` from default Kubernetes.
For more information about this behavior, refer to:
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection
# Links of interest
- https://istio.io/latest/docs/
- https://istiobyexample.dev/
- https://www.istioworkshop.io/
- https://istio.io/latest/news/
- https://istio.io/latest/blog/
- https://istio.io/latest/about/ecosystem/