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

Setup argo cd pipeline for auto deployment #235

Open
vishnoianil opened this issue Oct 3, 2024 · 0 comments
Open

Setup argo cd pipeline for auto deployment #235

vishnoianil opened this issue Oct 3, 2024 · 0 comments
Assignees
Labels
CI/CD enhancement New feature or request
Milestone

Comments

@vishnoianil
Copy link
Member

We need to setup two Argo CD pipelines :

  1. QA Deployment : Whenever any new code is merged in the main branch, it should be deployed in the qa.ui.instructlab.ai. Merge of the PR generates both UI and path service images and push it to quay.io and ghcr.io with main tag.

  2. Whenever any new release is created from release-* branch (e.g release-1.0) it should be auto deployed in the ui.instructlab.ai. New release is created using a new tag (and not a branch) (e.g v1.0.0-beta.2). Once the new release is create, it will generate images and push it to quay.io and ghcr.io with the same image tag as release tag, also it creates latest tag for the same images.

Notes:

  • In both the scenarios, restarting the pods should pull the latest image from the quay.io and deploy it.
  • Both the deployments depends on it's own set of environment variables. These environment variables need to be stored as encrypted secrets that is accessible by argo CD pipelines.
  • Also we can automate the the production deployment for ui.instructlab.ai, but having an option to manually trigger the production deployment can be helpful in multiple scenarios (hot patching).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD enhancement New feature or request
Projects
Status: Ready
Development

No branches or pull requests

2 participants