As a MLOps engineer I would like to use git as my source of truth for the deployment of my containerized model, so I can manage its lifecycle using a GitOps approach.

[LaVLaS]

Adding requirements that the PoC use case will be using ACM to manage the cluster configurations user GitOps and model lifecycle

Connected User Stories:

• As a MLOps engineer I would like that once my definition of the containerized model is defined in Git, ACM reconciles the desired state with my cluster at the edge. So I have a fully automated deployment mechanism.
• As a MLOps engineer I would also like to manage with ACM the infrastructure needed to deploy models so I can have a single management tool for the whole solution.

Acceptance Criteria:

• Add kustomize manifest to deploy on cluster git server for GitOps demos #28
• Document the GitOps process and how the cluster will be managed
• Cluster manifests are defined in a GitOps repo
• Model deployment and configuration for edge deployments are defined in a GitOps repo
• ACM Hub will apply manifests correctly when initiated by the Edge cluster
• Document the configuration and lifecycle of the Edge clustes

[adelton]

With #54 and #137 merged, isn't this actually done?

[LaVLaS]

Closing this out as that phase of the PoC has ended