Yeah I was mulling over something similar this morning.
K8S support is a cool feature to have, but there’s a few more pieces to the puzzle that could make the whole platform interoperability stuff amazing.
Serverless is one, utilising a charm to deploy a serverless workload to the platform of choice. But also more generic stuff that I want to be able to prototype, like charms that allow you to connect various disparate SaaS platforms together.
For example an interal website I’m currently working on, has a website in an S3 bucket, which talks to the AWS API Gateway, which in turn talks to a Lambda function which queries a Dyanmo DB table. It also uses AWS transcoder for video transcoding which in turn uses another Lambda function and another API gateway call and S3 for video storage.
Now I don’t think my example is particularly complex or uncommon, but it does require security group management, lambda function deployment and so on, all of which requires knowledge. I could tell you a few stories about AWS security groups at JPL… but I won’t!
On top of this we make loads of use of AWS Elastic Search, AWS K8S, AWS Cloudfront etc… but have also just started using Google Cloud… which is a whole other pain point and services that need to interoperate between the two.