this would likely break standard Istio configurations from the Istio documentation which rely on a shared istio gateway. This feature is visible in the PushContext.mergeGateways method as being used to control well supported such a configuration is as current Istio documentation focuses on the use of a single shared istio-ingressgateway in the istio-system control-plane namespace. As such, the Istio documentation gateway and Istio Gateway documentation should be updated to include warnings about the risks of shared ingress gateways. Furthermore, it may be worth- while to create an additional resource type for ingress

communicate important event details and collect aggregate attendance data. ● This PII will not be shared with any other third parties. ● This PII will be deleted right after the event wrap-up. PII from a. Keynotes: 1x b. Tech talks, lightning talks, workshops: 1x c. Event supporters: 1x 5. One shared mention at slack and social media for those who go above and beyond in the organization of the event

productivity, not decreasing it. 66 Abstracting Istio Adopting Istio The same way as we build libraries and interfaces to improve productivity, we need to build proper abstractions to maximize the added

features, connect all projects with istio. #IstioCon Common services are in core cluster Projects shared solution cluster • Different namespace • Project runs as tenant, need control rights Solution

Access-control Policy store, etc. ● AZ Control Plane ○ Syncs specs to workload K8s clusters in the AZ ○ Shared-Nothing Architecture ■ Hosts services catering to the AZ, e.g., AZ IPAM, Network Load-balancers

19 2022 Kick-off meeting September 26 2022 Status meeting #1 September 29 2022 Doc with issues shared with the Istio team. Subsequent issues added ad-hoc to the same doc. October 3 2022 Status meeting