Here’s a suggestion for the headline: “EMCO pushes the boundaries of application orchestration”. Possible text below (need to add a bit more text for GitOps, etc. Will get to it if I find the time – otherwise, please add.)
---
EMCO has a broad vision for end-to-end orchestration that includes not only *deployment of complex workloads* in a wide range of scenarios but also *automation of the infrastructure* needed by such workloads, ranging from networking and service mesh to application security. The focus on application infrastructure automation sets EMCO apart from most other orchestrators. The 22.06 release takes EMCO several steps forward in the supported range of deployment scenarios and in application security. As a leading example of the latter, when
Organize/converge/defragment the following points:
- When an application is deployed across multiple clusters with a service mesh, EMCO will now provision an intermediate CA in each relevant cluster to enable cross-cluster mTLS communication between its microservices.
...
- When an application’s service needs to be exposed outside the cluster, EMCO will provision a certificate for it.
- This release also includes Authorization APIs, which enable a user to configure access to the cluster services based on HTTP methods and routes.
The 22.06 release broadens the range of deployment scenarios that EMCO can handle:
...