Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rapidast migration information #2784

Open
Gregory-Pereira opened this issue Apr 17, 2023 · 1 comment
Open

Rapidast migration information #2784

Gregory-Pereira opened this issue Apr 17, 2023 · 1 comment

Comments

@Gregory-Pereira
Copy link
Member

Gregory-Pereira commented Apr 17, 2023

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:

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
Copy link
Member Author

Gregory-Pereira commented Apr 17, 2023

/cc @jeremychoi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant