What does the term "multi cloud" actually mean? - July 2

Anecdotal and survey data from the 2020 DevSecOps Survey on the topic of multi cloud for a blog post exploring this "new" thing:

What does multi-cloud mean to you?

Some apps are in AWS cloud and some in private self-hosted cloud. We are don't use multi cloud here. Not yet. Lots of we don’t use it yet. We don't. We only deploy to AWS because vendor lock-in and a failure to try out new the latest and greatest on other providers. I personally, am deploying to every cloud except AWS because they have free trials, best practices for kubernetes, great tutorials, and actually embrace the open source cloud native tooling I have become so accustomed to using. We don't, but vendor lock-in is one of the problems we need to solve to get the Director's buy-in for cloud. currently we are on GCP but like to move to AWS but we don't have the time / resource to start the migration neither a dedicated devops person. :( We should be able to replicate similar setup in other cloud provider. This is for worst case in disaster recovery. 2nd we don't want to be locked down in one cloud. Our org is going through a cloud platform change from AWS to Azure and that causes a lot of friction in code development Its a tool right, part of devops is knowing that there are many tools in the toolbox For us "multi-cloud" means simultaneously using multiple cloud providers, not just ability to migrate apps between them. Sometimes we deploy containers to multiple cloud providers, depending on the preferences or availability. The fact that we can do so without breaking our pipeline is vital. We don't, on purpose, because we do not subscribe to the vendor lock-in argument and therefore multi-cloud would require more resources than we feel it is worth. at the moment our code sits in physical servers and a small percentage or virtual servers, mainly because we're an enterprise security company. We have a bare metal kubernetes environment, aws, and azure. We seemlessly deploy to all through the same interfaces with an increasing reliance on gitlab Avoiding lockin is key for us currently. Being able to use any K8s engine is a important thing for us.

Checklist

• If you have a specific publish date in mind (please allow 3 weeks' lead time)
  • Include it in the issue title
  • Give the issue a due date of a minimum of 2 working days prior
  • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
• If time sensitive
  • Added ~"priority" label and supplied rationale in description
  • Mentioned @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive
  • Add sensitive label
  • Mention @nwoods to give her a heads up ASAP
• If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS and see the blog handbook for more on third-party posts
• Indicate if supporting an event or campaign
• Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)