The mig-agnosticd repository provides automation for deploying OpenShift Container Platform 3 and 4 environments specifically configured for testing and developing the Cluster Application Migration Tool. Rather than implementing deployment logic directly, this repository serves as a collection of prescriptive configuration files and shell scripts that drive the upstream agnosticd project from Red Hat Communities of Practice, which handles the actual infrastructure provisioning and orchestration work.
The repository is organized into two main deployment paths corresponding to different OpenShift versions. The 3.x directory contains configurations for deploying OpenShift 3.11 clusters on AWS using OpenShift Ansible and CloudFormation for infrastructure management. These clusters are intended to serve as source environments for migration testing. The 4.x directory provides configurations for OpenShift 4.1 clusters deployed on AWS using the OpenShift Installer with Terraform-based infrastructure provisioning, designed to function as destination clusters for migration workflows.
Both deployment paths include installation of migration-related components beyond the base OpenShift cluster. These include Velero for backup and restore functionality, along with custom plugins from the Konveyor project including the openshift-migration-plugin and openshift-velero-plugin. The 3.x deployments also install a forked version of Restic for backup storage. The 4.x deployments additionally include the Migration CRDs and Controllers from mig-controller and the Migration UI from mig-ui, providing a complete migration platform on the destination cluster.
The provisioning workflow relies on agnosticd's Ansible roles and operators rather than direct Kubernetes manifests. Installation of Velero and migration components is handled through the velero-operator and mig-operator, which are deployed as regular Kubernetes Deployments rather than through the Operator Lifecycle Manager. These operators then create the necessary custom resources to configure their respective applications.
Users must meet several prerequisites before deploying environments. AWS access is required with admin privileges for OCP 4.x deployments, and users need access to a Route53 hosted zone to provide domain names for clusters. The agnosticd repository must be checked out separately and referenced via the AGNOSTICD_HOME environment variable. Configuration requires creating secret files from provided samples, with version-specific secret files for OCP 3 and OCP 4 deployments containing AWS credentials and other sensitive configuration.
The repository is written primarily in Shell and classified across multiple infrastructure and deployment-related categories including Kubernetes, configuration management, cloud environments, and infrastructure automation. It maintains connections to related Konveyor project repositories including mig-ui, mig-controller, and velero-io/velero through overlapping contributors. The codebase supports optional features like FIPS mode for OCP 4 deployments and includes Python virtualenv support for managing Ansible dependencies, with specific constraints documented to address compatibility issues with PyYAML versions.
