title: GitLab HA with Kubernetes and Gluster
body: <p>I currently have GitLab omnibus setup on Docker. I plan to have HA for the same by adding it to Kubernetes and have persistence using Gluster. I have played around configuring Kubernetes with Gluster. Now it's time to bring GitLab into Kubernetes. GitLab uses PostgreSQL as the default db.</p>
  
  <p>My query is that to implement HA, should i<br>
  a) split GitLab into GitLab application and PostgreSQL container, and then run both (Application and DB) in their own cluster of pods i.e., separate <em>deployments</em> of replicas of GitLab app and PostgreSQL?<br>
  OR<br>
  b) keep using the omnibus installer and just have replicas of this single, standalone container?</p>
  
  <p>Does it really make any difference whether<br>
  1) writes happen to a db cluster exposed via service to the GitLab app<br>
  OR<br>
  2) writes happening directly to the omnibus GitLab container (which has db within itself)</p>
  
  <p>Just want to make sure that i don't unnecessarily end up making the setup complex. Having GitLab in Kubernetes along with Gluster already makes things a little complex. So does splitting app and db makes sense or just the omnibus setup will suffice? Concerned about concurrent writes to db.</p>