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

Automate Deployment with GitHub Actions for Helm #225

Open
6 tasks
paulpascal opened this issue Nov 13, 2024 · 0 comments · May be fixed by #226
Open
6 tasks

Automate Deployment with GitHub Actions for Helm #225

paulpascal opened this issue Nov 13, 2024 · 0 comments · May be fixed by #226
Assignees

Comments

@paulpascal
Copy link
Contributor

paulpascal commented Nov 13, 2024

Description

Automate the deployment process for the new service using GitHub Actions, with the goal of reducing manual intervention and minimizing errors. This automation will streamline the deployment pipeline and allow developers to focus on debugging when necessary, rather than managing deployment steps manually.

Context

We need to automated deployment process to prevent potential issues caused by manual deployment. One suggestion by @Hareet is using GitHub Actions with Helm commands for deployment automation. This approach will allow us to deploy consistently and minimize human error in the deployment pipeline.

Action Items

  • Set up GitHub Action: Create a GitHub Action workflow to automate Helm deployments.
  • Manual Trigger Option: Configure a manual trigger for deployments, allowing control over when deployments occur.
  • Use of Environment Variables: Replace kubecontext token with a secure environment variable within GitHub Actions for authentication.
  • Testing: Build and test the automation with proper credentials, ensuring it runs as expected.
  • Update documentation to outline the steps for using this automation.
  • If possible - delete deploy branch to avoid future confusion of how to push to prod
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

Successfully merging a pull request may close this issue.

2 participants