title: Gitlab-CI, Review Apps, GKE, the good way?
body: <p>I'm starting with Kubernetes (through GKE) and I want to setup Gitlab <a href="https://about.gitlab.com/product/review-apps/" rel="nofollow noreferrer">Review Apps</a>.
  My use case is quite simple. I've read tons of articles but I could not find clear explanations and best practices on the way to do it. This is the reason why I'm asking here.</p>
  
  <p>Here is what I want to achieve :</p>
  
  <ul>
  <li>I have a PHP application, based on Symfony4, versioned on my Gitlab CE instance (self-hosted)</li>
  <li>I setup my Kubernetes using GKE into Gitlab</li>
  <li>I want, on each merge request, deploy a new environment on my cluster where I am able to test the application and the new feature (this is the principle of Review Apps).</li>
  </ul>
  
  <p>As far as I read, I've only found simple implementations of it. What I want to do, is deploy to a new LAMP (or LEMP) environment to test my new feature.</p>
  
  <p>The thing that I don't understand is how to proceed to deploy my application.
  I'm able to write Docker files, store them on mi Gitlab registry, etc ...
  In my use case, what is the best way to proceed?</p>
  
  <ul>
  <li><p>In my application repository, do I have to store a Docker file which includes all my LAMP configuration (a complete image with all my LAMP setup)? I don't like this approach, it seems strange to me.</p></li>
  <li><p>Do I have to store different custom images (for Apache, MySQL, PHP-FPM, Redis) on my registry and call them and deploy them on GKE during <code>review</code> Stage in my <code>gitlab-cy.yml</code> file?</p></li>
  </ul>
  
  <p>I'm a little bit stuck on that and I can't share code because it's more about the way to handle everything.</p>
  
  <p>If you have any explanations to help me, it would be great!
  I can, of course, explain a little bit more if needed!</p>
  
  <p>Thanks a lot for your help.</p>
  
  <p>Happy new year!</p>