Here is the list of features that will be released at end of this year.
Complex applications would have front-end microservice and backend microservices. Backend microservices may be distributed across multiple clusters. This feature enables connectivity among the microservices in different clusters by automating the ISTIO configuration. Also, it automates the configuration of the ingress proxy to expose the frontend microservice to external users and route the traffic from the external users to the frontend microservice. As a test case, we A key functionality of EMCO is to deploy any microservice to an appropriate cluster and set up the network communication from the deployed microservice to another microservice as needed. We will use EMCO to deploy Google's Online Boutique which consists of a 10-tier microservices application. This application is a web-based e-commerce app where users can browse items, add them to the cart, and purchase them. Google uses this application to demonstrate the use of technologies like Kubernetes/GKE and Istio. The feature will ensure that EMCO can deploy these microservices properly and can set up a communication channel between these services microservices seamlessly through integration with Istio. The work involves creating helm charts for GMS, deploying GMS, and automatically creating data traffic controller intents for the GMS, and interacting with Istio control plane to deploy the intents and , inject envoy into each microservice POD, and set up the network communication between the deployed microservices as well as the network communication from external users to the frontend microservice.
Helm provides a hook mechanism to allow the users to specify additional action/logic at certain points in an application's life cycle. Helm supports pre-install, post-install, pre-delete, post-delete, pre-update, and post-update hooks. Add support of these hooks in EMCO.
...