Hmm… what exactly is a hybrid cloud workload for you? Do you really want to e.g- distribute parts of an application over multiple clouds, or do you want to run different cloud estates?
The first is pretty hard, the second is pretty trivial.
Problems usually arise when you either want tooling that allows you to address both your estates in an uniform way or when you want to be able to move applications between clouds without much effort - hint… they need to be desined and built for that in the first place.
Going hybrid - cloud + on-prem can be pretty trivial if you buy into the cloud provider model of connecting the two estates. Having baseline network connectivity makes most problems disappear. If you go without that it gets hard to get things right in a secure and reliable way.
I don’t want to pitch here, but you could take a look at the
reference architectures we provide - you can have many “resouce planes” as you like, turning that into a multi- or hybrid scenario immediately. Feel free to exchange any logos in there for ones that fit your world better. You can get inspiration from the
community tooling landscape.