Intelligent Software Delivery (ISD) for Argo
OpsMx’s “Intelligent Software Delivery(ISD)” is designed to help release software faster, with fewer errors, and with minimal human intervention to create a better end-customer experience and free up time and Manpower for businesses to scale and Innovate.
OpsMx Intelligent Software Delivery(ISD) for Argo offers the power of GitOps-based deployments with ease and minimal learning curve along with AI/ML-driven automation for approvals, verification, security checks, and compliances for comprehensive visibility, auditability, and fine-grained control on your continuous delivery (CD) process, with no vendor lock-in.
OpsMx ISD for Argo is a declarative GitOps continuous deployment system for Kubernetes with centralized management of deployments. It extends Argo CD with advanced capabilities including Enterprise user management, Role-based Access Control, integrations, management of multiple Argo instances, and ML-based verification for advanced deployments such as blue-green, canary analysis, experimentation, and progressive delivery features.
The key benefits you would see as a result of using “ISD for Argo” are as follows:
- Low Operational Cost
- Simple Hassle-free secure Enterprise distribution
- Maintaining multiple Argo instances and simplified life-cycle management
- Get 24/7/365 support from Argo and CD experts
- Get 99.99 SLA on SoC 2 certified cloud/SaaS solution
- GitOps for Enterprise
- Ensure enterprise user management and RBAC is implemented
- Support global teams with clusters behind firewalls
- Get advanced enterprise tool integrations (like JIRA, SNOW etc)
- Enforce compliance and security policies as part of the end-to-end work in an automated fashion
- Scale GitOps For Your Developers and SRE
- Get pre-build validated workflow template for enterprise use cases like Terraform, Ansible deployments
- Deploy safe with validated workflow templates for blue-green/canary/multi-service deployments with automated machine learning based analysis of rollouts
- Migration Assistance
- OpsMx CD experts guide your migration of app delivery to Argo
The following are the different features of the “ISD for Argo”.
- Hardened Distribution of Argo
- Ready to use Enterprise user management, security, integrations, and advanced templates
- Manage multiple Argo instances securely
- 100% auditability and storage of deployments events for retrieval
- Insights and DORA metrics to measure DevOps performance
- Advanced approval with integrated data sources
- Automated enforcement of Compliance and security policies
- Advanced automated ML based progress rollout analysis
The figure below depicts the component view of the “ISD for Argo” architecture.
As shown in the above “ISD for Argo Architecture” diagram, Autopilot(ISD UI) and Master OEA are installed in the same Kubernetes cluster. Autopilot communicates with Master OEA through an Agent. If “Worker OEAs” or “Open Source Argos” are hosted in different Kubernetes clusters behind a firewall, where there is no direct access for Autopilot to Integrate with Argo Instances, you need Agents to enable communication between Autopilot and Argo Instances. The communication between Autopilot and Agents will happen through a controller.
The details about each of the “ISD for Argo” components are as follows.
Autopilot: This is the “Intelligent Software Delivery (ISD) UI which connects the “Customer OSS Argo” or “Worker OEA” with one or more agents.
Master OEA: It is the “OpsMx Enterprise Argo” which is installed in the same cluster where Autopilot(ISD UI) is installed.
Worker OEA: It is the “OpsMx Enterprise Argo” which consists of only Argo components intended to be used with Agent.
Agent: The agent runs inside a customer’s private network and serves as a secure point of contact between ISD and the customer’s network environment. The Agent is configured to communicate with specific services (Kubernetes, Jenkins, etc.) within a customer's security domain.
Controller: The Controller runs outside of the customer’s private network(typically in the same cluster as ISD) while an Agent runs inside a customer’s private network. ISD receives service information from the controller and allows a user to connect an Agent service to an Argo instance. Connecting an Agent service to an Argo instance allows access to crucial information such as per-service health along with overall Agent health.