apps icon indicating copy to clipboard operation
apps copied to clipboard

Rapidast migration information

Open Gregory-Pereira opened this issue 2 years ago • 1 comments

This issue is supposed to provide some clarity on how the rapiDAST team will migrate to another gitops repo.

This migration should look similar to the aggregate changes of these two prs: the infra changes, and operator deployment. The following is a list of the files introduced in the PR and how these kubernetes resources map to changes in Gitops:

The first PR:

  • creates the psse-research group
  • creates the rapidast namespace with a medium ResourceQuota and a project admin rolebinding for that ns (namespace file)
  • creates the project admin rolebinding for the namespace (applies rbac for group to ns)
  • deploys the group to the cluster(https://github.com/operate-first/apps/pull/1572/files#diff-ae0580f327d0b9edc25fa1f2bc65b48e42be46cb92319652b231586ee957b37aR41)
  • deploys the namespace to the cluster (https://github.com/operate-first/apps/pull/1572/files#diff-a6a0c818898dcaa8c31ccd32e1d2004a2fb977c7afc512c89570b9fdc77accbfR61)
    • ignore other changes in that cluster-scope/overlays/prod/moc/smaug/kustomization.yaml file, they are just alphabetically sorting the bundles already deployed to the cluster

The second PR:

  • the CatalogSource for the rapidast operator (file)
  • the OperatorGroup for the rapdiast namespace in which the operator will be deployed (file)
  • the Subscription to the rapidast operator using above CatalogSource and OperatorGroup (file)
  • Modifications to the kustomization overlay that deploys those 3 resources to the Smaug cluster (file)

Our argocd cluster-resources-smaug application watches the Smaug kustomization overlay (operate-first/apps/cluster-scope/overlays/prod/moc/smaug/kustomization.yaml). It builds and deploys everything in this file, as well as what it builds from the MOC common overlay (operate-first/apps/cluster-scope/overlays/prod/moc/common/kustomization.yaml), because it is referenced from the kustomization overlay. Between these two overlays that get built, all the changes in git from those 2 PRs get picked up by our Argocd Applications and deployed to the openshift cluster.

Gregory-Pereira avatar Apr 17 '23 16:04 Gregory-Pereira

/cc @jeremychoi

Gregory-Pereira avatar Apr 17 '23 16:04 Gregory-Pereira