Redesign Proposal #IstioCon #IstioCon “First and foremost: as a potential contributor, your changes and ideas are welcome at any hour of the day or night, weekdays, weekends, and holidays. Please ● Viewing changes as if they were live ● Linter is pretty specific ● Don't forget to update/create a test if the page changed is tested! #IstioCon Run make lint locally to verify changes and check

without context. GitHub asks developers and maintainers whether a pull request has user facing changes. ● If it does, the developer can easily add a release note. ● If it doesn’t, then the developer Notes #IstioCon Release Notes: As a result... ● Release notes are thought of up-front as part of changes, with context by the people who know the most about what’s being changed. ● Release notes and

practices. Description Istio’s documentation is rather large but also has some gaps related to recent changes. Some blog posts describe security features that are now deprecated and some security features are Review the recommendations in previous findings referenced above that highlight many of the possible changes that are needed to further lock down the Default profile. Consider providing a hardened profile when

io/latest/blog/2020/tradewinds-2020/ #IstioCon Operational Excellence ● Detecting backwards incompatible changes ● Measuring developer efficiency ○ Test flakes ○ Feature and code coverage ● Feature promotion

Istio to Meet 5G Requirements 13 ©2021 Aspen Mesh. All rights reserved. ● Istio architectural changes ● SPIFFE only certificates ● Configuring workload certificate TTLs ● RSA to ECC migration ●

packet inspection (DPI) ○ DDoS defense ○ Firewall ● Lack dedicated gateway support (architectural changes) ○ No separating out the gateway used for untrusted user traffic from the internal mesh traffic

Istio? #IstioCon How to Manage AwesomeRPC Traffic in Istio? Pilot Envoy Code changes at the Pilot side: ● Add AwesomeRPC support in VirtualService API ● Generate LDS/RDS for Envoy