The approach we have taken is to create independent clusters with a common LoadBalancer.
Basically, the LB decides which kubernetes cluster will serve your request and once you're in a k8s cluster, you stay there.
You don't have the control-plane that the federation provides and a bit of overhead managing clusters independently, but we have automated the majority of the process. On the other hand, debugging is way easier and we don't suffer from weird latencies between clusters (weird because sometimes a request will go to a different cluster without any apparent reason <-- I'm sure there's one, but none that you could see/expect, hence debugging).
My people's time is more important than your complex system.
But they have been... for years! We've been creating fat jars to deploy services for a while already.
First Dropwizard and then Spring boot has been leading the way. But Micro is not about building a microservice, is about building a microservice ecosystem.
We agree that government is not the right way of solving this issue, but it's incredibly easy to have images to show up that are far from appropriate for children... or that you would share at the table
What about GCP? can my agents deploy to my GCP account using Neptune?