Answers: <p>I'm looking at <a href="https://tilt.dev/" rel="nofollow noreferrer">tilt</a>, and so far it's awesome for this.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-07-17T18:49:24.427Z
Answers: 2021-07-17T18:49:24.427Z
Answers: Aaron
Answers: <p>I would say the reason you are wanting to develop against Kubernetes locally is to see how the application works with within the pod, and how it interacts with other dependencies inside the Kubernetes instance.</p>
  <p>In this case you want to go for speed of getting the code into the container. Here you want something like <a href="https://docs.tilt.dev/live_update_tutorial.html" rel="nofollow noreferrer">Tilt Live Update</a> which will run your build of your code locally, and then sync it into the running container. This avoids needing to build a container and deploy a new resource each time.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-07-20T15:50:59.830Z
Answers: 2021-07-20T15:50:59.830Z
Answers: Matthew Hodgkins
Answers: <p>It's really up to your personal preference, but for minikube you can certainly follow the same standards that you would for production.</p>
  <p>If your production environment will use some sort of volume mount for your application code, then follow that same workflow for local dev and just have a pod running that mounts to your local code.</p>
  <p>If your production environment expects that application code inside of the container, then set up a local registry in minikube, and build/push images into that registry.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-07-15T18:34:08.130Z
Answers: 2021-07-15T18:34:08.130Z
Answers: Jon W
Body: <p>When using kubernetes with minkube locally, what is best practice for a development environment?</p>
  <p>When using docker, in development I have mounted a volume with the source code, so I can modify code and see the changes in real-time without rebuilding the image. In production I bake the app code into the image for obvious reasons.</p>
  <p>What do people do when using k8s/minikube for development. Same idea? Mount a volume pointing to where the app code lives on the host machine so they don't have to push images? If so isn't editing the deployment image the main way the pods update?</p>
  
Comments: CC BY-SA 4.0
Comments: 2021-07-17T21:47:31.477Z
Comments: Hi Aaron, you can look into https://skaffold.dev/
Comments: rohatgisanat
Comments: CC BY-SA 4.0
Comments: 2021-07-18T11:21:47.600Z
Comments: This looks promising too.
Comments: Aaron
Tags: <docker><kubernetes><environments>
Title: Best Practice for Kubernetes Development Environment
UserDisplayName: Aaron
ThreadText: # Best Practice for Kubernetes Development Environment
  
  (Asked by: username_0 on 2021-07-13)
  
  When using kubernetes with minkube locally, what is best practice for a development environment?
  
  When using docker, in development I have mounted a volume with the source code, so I can modify code and see the changes in real-time without rebuilding the image. In production I bake the app code into the image for obvious reasons.
  
  What do people do when using k8s/minikube for development. Same idea? Mount a volume pointing to where the app code lives on the host machine so they don't have to push images? If so isn't editing the deployment image the main way the pods update?
  
  **Tags:** docker, kubernetes, environments
  
  > **Comments:**
  > **username_1**: Hi username_0, you can look into https://skaffold.dev/  
  > **username_0**: This looks promising too.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_3 on 2021-07-15. Score: 1
  
  It's really up to your personal preference, but for minikube you can certainly follow the same standards that you would for production.
  
  If your production environment will use some sort of volume mount for your application code, then follow that same workflow for local dev and just have a pod running that mounts to your local code.
  
  If your production environment expects that application code inside of the container, then set up a local registry in minikube, and build/push images into that registry.
  
  
  ---
  
  ### Answer by username_0 on 2021-07-17. Score: 0
  
  I'm looking at [tilt](https://tilt.dev/), and so far it's awesome for this.
  
  
  ---
  
  ### Answer by username_2 on 2021-07-20. Score: 0
  
  I would say the reason you are wanting to develop against Kubernetes locally is to see how the application works with within the pod, and how it interacts with other dependencies inside the Kubernetes instance.
  
  In this case you want to go for speed of getting the code into the container. Here you want something like [Tilt Live Update](https://docs.tilt.dev/live_update_tutorial.html) which will run your build of your code locally, and then sync it into the running container. This avoids needing to build a container and deploy a new resource each time.
  
  
  ---
  
  