You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
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.The text was updated successfully, but these errors were encountered: