DRAFT
Here’s a suggestion for the headline: “EMCO pushes the boundaries of application orchestration”.
---
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.
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:
- EMCO can now leverage Google Cloud (via Anthos GitOps) as a target for workloads. This increases flexibility and resilience for the user/operator by integrating with additional clouds.
- EMCO can now automatically trigger user-defined workflows at multiple stages of an application's lifecycle (using Temporal). This is a step towards automation and integration, allowing users/operators to do less outside of EMCO.
This release reinforces the position of EMCO as a leading open source orchestrator that goes beyond the basics by orchestrating the infrastructure needs of modern cloud-native applications, including security, in addition to catering to the complex deployment scenarios that they require. The EMCO community invites you to try out the latest release and join us in shaping the future of orchestration.