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

Question: best place to put "local environment" startup scripts ? (not Helm) #216

Open
lerenn opened this issue Feb 15, 2023 · 1 comment

Comments

@lerenn
Copy link

lerenn commented Feb 15, 2023

Hello !

A question here: we have a local environment that we would like to put in the go repository where it start a minikube and add a database. These are not correlated with the helm placed in deployment.

Where would you put them ? Actually, we put the m under deployment/local, but it seems kinda wrong as it is not directly linked to application deployment.

@lerenn lerenn changed the title Best place to put "local environment" startup script (no Helm) Best place to put "local environment" startup scripts (not Helm) Feb 15, 2023
@lerenn lerenn changed the title Best place to put "local environment" startup scripts (not Helm) Question: best place to put "local environment" startup scripts ? (not Helm) Feb 15, 2023
@OneCricketeer
Copy link

How about scripts/minikube-deploy.sh, called from make minikube-deploy, which uses deploy/k8s folder which contains Helm Charts?

Otherwise, you can create build/ci folder for your project (i.e. use Github Actions) to create a Docker image, then push that to a Registry, then have a completely separate deployment Git repo (unrelated to Go, as you said) that could use something like ArgoCD to pull that image and update your cluster from your "deploy repo" after updating the image tag.

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

2 participants