dev - 2023/10/14 #66

Merged
ofilter merged 24 commits from dev into main 2023-10-14 13:06:28 +02:00
Showing only changes of commit 84b71d9751 - Show all commits

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/