faas-federation is an implementation of the faas-provider which can be used to unify one or more OpenFaaS clusters under a single API.
Why do we need this?
This project exists to join together two or more distinct OpenFaaS clusters.
- Multi-region - east/west
Get a single API / control-plane for one or more clusters split by location, such as east/west.
- Edge locations
You may have one or more edge locations (or even ARM/IoT OpenFaaS installations). You can join them together under a single set of credentials and control plane.
- Varying provider types
You can connect two or more different OpenFaaS provider types together. For instance: Kubernetes (faas-netes) and Lambda (faas-lambda). This means you can have a single, centralized control-plane but deploy to both AWS Lambda and Kubernetes at the same time.
faas-federation can replace your provider in your existing OpenFaaS deployment.
More coming soon.
Coming soon: deploy OpenFaaS with two separate
See also: example of Kubernetes and AWS Lambda federated configuration in the sample helm chart.
|federation.provider_name||route the request based on the provider name i.e.
All configuration is managed using environment variables
||comma separated list of provider URLs i.e.
||default provider URLs used when no deployment constraints are matched i.e.
Idea by Alex Ellis and Edward Wilde.