Home > Back-end >  Gitlab - Using one self-hosted instance to deploy on several cloud providers?
Gitlab - Using one self-hosted instance to deploy on several cloud providers?

Time:03-19

Is it a 'good idea' to use one self-hosted instance of Gitlab (let's say on Azure) and use it to deploy on multiple clouds (e.g AWS, Azure, GCP) ? What is first coming to my mind is that it needs a private network link between the cloud providers so that the private self-hosted agents can communicate with the self-hosted Gitlab instance.

I don't find architecture examples introducing this kind of solution.

CodePudding user response:

There is not necessarily any reason why you cannot deploy solutions on multiple clouds, irrespective of where your GitLab runners happen to be hosted. Your runners don't have to be hosted in the cloud to which you are deploying. You can even deploy to all clouds from GitLab.com hosted runners, for example.

  • Related