Answers: <p>Check out the GitLab Operations Dashboard feature (<a href="https://docs.gitlab.com/ee/user/operations_dashboard/" rel="nofollow noreferrer">https://docs.gitlab.com/ee/user/operations_dashboard/</a>)</p>
  
  <p>There is a screenshot on that page, too, so you can get an idea of it.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-04-12T00:07:28.477Z
Answers: Thanks for the suggestion.  It caps out at a very small number of projects though and its only personal / user specific.  Its not very useful for a company/team at any scale (yet).  I do know that they are working on scaling it though for greater purposes :).  So, fingers crossed for the future!
Answers: John Humphreys
Answers: CC BY-SA 4.0
Answers: 2020-04-12T00:15:43.733Z
Answers: Got it, thanks for the data!
Answers: Aleksey Tsalolikhin
Answers: CC BY-SA 4.0
Answers: 2020-04-11T19:03:41.017Z
Answers: 2020-04-11T19:03:41.017Z
Answers: Aleksey Tsalolikhin
Answers: <p>Regarding modern CD tools, such as Spinnaker, Argo, Flux, Jenkins X (depending on your stack and use case - most are k8s specific) - they will help you with roll-out of any specific code base (set of artifacts) to a large number of nodes / instances. However, they wouldn't help you with versioning or keeping track of versioning. Essentially, they would help you to deploy whichever version you tell them to deploy to a large scale. </p>
  
  <p>I'm currently working on a project - <a href="https://relizahub.com" rel="nofollow noreferrer">https://relizahub.com</a> - which integrates with any CI/CD solution to solve the problem of versioning there. Here's my latest demo video on approvals across different environments - <a href="https://www.youtube.com/watch?v=PzdZjMby6Is" rel="nofollow noreferrer">https://www.youtube.com/watch?v=PzdZjMby6Is</a>. It may help with a versioning issue and seeing what version you have at which instance and when it was deployed.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-04-13T13:07:42.960Z
Answers: 2020-04-13T13:07:42.960Z
Answers: taleodor
Body: <p>Let's say I have a SaaS style project (similar to Databricks).  We may make release 2.0.0 of this project, have automated testing and deployment to dev, automated promotion to nonprod, etc.</p>
  
  <p>In production, I may have 200 <strong>instances</strong> of it running though.</p>
  
  <p>What is the best way using GitLab CI to manage 200 instances/production environments? Obviously you wouldn't want 200 branches with deployments controlled by merges/etc... I assume.</p>
  
  <p>How can you get a good overview over all of these environments and ensure they're deployed completely/view their versions and roll-out progress, ensure smoke tests completed for a successful pipeline/etc?</p>
  
  <p>Its been implied to me that Spinnaker may be a good tool to plug this gap.  Can someone explain how that is if so?  Are there any better options?</p>
  
Tags: <deployment><gitlab><release><environments><spinnaker>
Title: GUI over GitLab CI Environment Deployments With Multiple Instances?
UserDisplayName: John Humphreys
ThreadText: # GUI over GitLab CI Environment Deployments With Multiple Instances?
  
  (Asked by: username_0 on 2020-01-22)
  
  Let's say I have a SaaS style project (similar to Databricks). We may make release 2.0.0 of this project, have automated testing and deployment to dev, automated promotion to nonprod, etc.
  
  In production, I may have 200 **instances** of it running though.
  
  What is the best way using GitLab CI to manage 200 instances/production environments? Obviously you wouldn't want 200 branches with deployments controlled by merges/etc... I assume.
  
  How can you get a good overview over all of these environments and ensure they're deployed completely/view their versions and roll-out progress, ensure smoke tests completed for a successful pipeline/etc?
  
  Its been implied to me that Spinnaker may be a good tool to plug this gap. Can someone explain how that is if so? Are there any better options?
  
  **Tags:** deployment, gitlab, release, environments, spinnaker
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2020-04-11. Score: 1
  
  Check out the GitLab Operations Dashboard feature (<https://docs.gitlab.com/ee/user/operations_dashboard/>)
  
  There is a screenshot on that page, too, so you can get an idea of it.
  
  > **Comments:**
  > **username_0**: Thanks for the suggestion.  It caps out at a very small number of projects though and its only personal / user specific.  Its not very useful for a company/team at any scale (yet).  I do know that they are working on scaling it though for greater purposes :).  So, fingers crossed for the future!  
  > **username_1**: Got it, thanks for the data!  
  
  ---
  
  ### Answer by username_2 on 2020-04-13. Score: 0
  
  Regarding modern CD tools, such as Spinnaker, Argo, Flux, Jenkins X (depending on your stack and use case - most are k8s specific) - they will help you with roll-out of any specific code base (set of artifacts) to a large number of nodes / instances. However, they wouldn't help you with versioning or keeping track of versioning. Essentially, they would help you to deploy whichever version you tell them to deploy to a large scale.
  
  I'm currently working on a project - <https://relizahub.com> - which integrates with any CI/CD solution to solve the problem of versioning there. Here's my latest demo video on approvals across different environments - <https://www.youtube.com/watch?v=PzdZjMby6Is>. It may help with a versioning issue and seeing what version you have at which instance and when it was deployed.
  
  
  ---
  
  