specifications ● Kubernetes shortcomings with sidecar containers ○ Controlling containers lifecycle ○ Autoscaling pods with sidecar containers ● Are you prepared to handle Istio? ● A full mesh is sidecar containers Stabilizing Istio Pod A is the Kubernetes atomic unit Pod App container Sidecar container Pods are the atomic unit, not containers. 15 15 Shortcoming 1: Controlling the running order for containers Stabilizing Istio Kubernetes lacks good control APIs to customize the containers lifecycle in a pod. There is no official way to instruct

Istio Client-Side Bypasses 014 Low Sidecar Envoy Administrative Interface Exposed To Workload Containers 018 Low DestinationRules Without CA Certificates Field Do Not Validate Certificates 019 Low Default Google / NCC Group Confidential Finding Sidecar Envoy Administrative Interface Exposed To Workload Containers Risk Low Impact: Low, Exploitability: Medium Identifier NCC-GOIST2005-018 Category Access Controls istio/install/gcp/bootstrap/gcp_envoy_bootstrap.json • istio/pkg/config/mesh/mesh.go Impact Workload containers can access potentially sensitive configuration data and manipulate the sidecar Envoy proxy process

v1 spec: containers: - image: rating-v1 ... --- kind: Deployment metadata: name: rating-v2 spec: replicas: 3 template: metadata: labels: app: rating version: v2 spec: containers: - image: rating-v2

version: v1 spec: containers: - image: rating- v1 kind: Deployment metadata: name: rating-v2 spec: replicas: 3 template: metadata: labels: app: rating version: v2 spec: containers: - image: rating-

existing fuzzing set up. At the start of the audit, we made the following observations: ● Istio is integrated into OSS-Fuzz with 63 fuzzers running continuously. ● All fuzzers are hosted in the Istio repository need more data, but only the provenance would need improvement. The slsa-github-generator can be integrated into Istio's build pipeline as a first step to start 53 Istio Security Audit, 2023 work on provenance

Istio Ingress Istio Egress Istio 1.6 Istio 1.6 Service Mesh Operator Lessons Learned 1. Init containers maybe not the best option • NET_RAW and NET_ADMIN • Traffic failures due to init restarts (#16768)

policies in the same way, across compute environments ● Observability ○ See VM metrics alongside containers ● Extensibility #IstioCon Why Should Istio Support VMs ● ≈ Why VMs? ○ Technical reasons ■

Logical Service for Developers ○ Multi-cluster Identity ○ Multi-region Endpoint ○ Istio config integrated with gitops deployment ○ Init modifications to prevent proxy startup race conditions Thank You