Solo.io, a cloud infrastructure startup, blogs about API gateways, service mesh, Istio, Envoy and multi-cluster Kubernetes.
HN mostly links it from the company's hiring posts and in discussions of multi-cluster Kubernetes federation and its customer list.
solo.io | https://www.solo.io | Boston/Cambridge | Full-time | Back-end Software Engineer
We are looking for extraordinary engineering talent to continue our mission to help large enterprises migrate to microservices and modern cloud infrastructure. Some of our products include a cloud-native API gateway built on top of Envoy (Gloo Edge), a Service Mesh control plane for multi-cluster and multi-mesh management (Gloo Mesh), and a Developer Portal to help publish your APIs and speed up developer onboarding (Gloo Portal).
Our tech-stack is primarily working with Go, docker, K8s, Envoy and Istio. There's also some exposure to WebAssembly and C++. Many of our products are open source, or have large open source components, check out our GitHub if you're interested in how we code - https://github.com/solo-io
We are also hiring for field engineers all over the world, as well as a documentation lead - https://www.solo.io/company/careers/
solo.io | Cambridge, MA or remote | Full Time | https://www.solo.io
solo is an exciting new startup (https://trueventures.com/solo-future-of-cloud/, https://www.solo.io/single-post/2017/11/01/Solo’s-seed-funding-round-supporting-its-groundbreaking-vision-for-the-future-of-the-cloud), currently we are hiring:
* systems engineer (https://www.solo.io/system-software-engineer)
* UX Engineer (https://www.solo.io/copy-of-system-software-engineer)
In this role you'll work with a wide rage of tech like: Serverless, Docker, Kubernetes, Mesos, Linux, Unikernels, AWS and Google Cloud, Azure, ectd, istio, Golang and more. We don't expect someone coming into the role to have experience with everything, but would like someone that is excited to learn!
checkout our past projects:
- unik (https://github.com/cf-unik/unik)
- squash (https://github.com/solo-io/squash)
Multi-cluster kubernetes federation could be the answer (where a "cluster" could be as tiny as a k3s instance running on your Raspberry Pi).
However could mean you need one vendor to provide the control-plane software for your vendor-agnostic solution.
Nobody has nailed it yet though, AFAIK, but both Rancher and Gloo Federation look promising.
Related reading:
https://github.com/kubernetes-sigs/kubefed
https://rancher.com/products/rancher/multi-cluster-management/
https://www.solo.io/blog/introducing-gloo-federation-for-multi-cluster-management/
We have a list of our end users and customers listed here along with links to their talks and blogs about their experience with gloo https://www.solo.io/customers/