Catalog Details
CATEGORY
DeploymentCREATED BY
UPDATED AT
June 05, 2024VERSION
1.0
What this pattern does:
Cryptographic operations are among the most compute-intensive and critical operations when it comes to secured connections. Istio uses Envoy as the “gateways/sidecar” to handle secure connections and intercept the traffic. Depending upon use cases, when an ingress gateway must handle a large number of incoming TLS and secured service-to-service connections through sidecar proxies, the load on Envoy increases. The potential performance depends on many factors, such as size of the cpuset on which Envoy is running, incoming traffic patterns, and key size. These factors can impact Envoy serving many new incoming TLS requests. To achieve performance improvements and accelerated handshakes, a new feature was introduced in Envoy 1.20 and Istio 1.14. It can be achieved with 3rd Gen Intel® Xeon® Scalable processors, the Intel® Integrated Performance Primitives (Intel® IPP) crypto library, CryptoMB Private Key Provider Method support in Envoy, and Private Key Provider configuration in Istio using ProxyConfig.
Caveats and Consideration:
Ensure networking is setup properly and correct annotation are applied to each resource for custom Intel configuration
Compatibility:
Recent Discussions with "meshery" Tag
- Jun 04 | How to setup Meshery Operator for local machine
- Jun 04 | Error on terminal when I ran `mesheryctl system start`
- Jun 04 | No connection shown in Docker Desktop Meshery extension
- Jun 04 | Showing no connections in meshery playground as well as in Docker meshery extension
- Jun 03 | Error in Meshery Server logs
- Jun 03 | Looking for Meshmate for first PR
- Jun 02 | Bug in MesheryPlayground production website in Deploying and Removing Adapters
- Jun 01 | Error encountered when trying to refresh after deploying adapter in settings in meshery playground
- Apr 14 | Unable to deploy meshery to minikube
- May 30 | Looking for a meshmate to help with first PR