How to set up OpenFaaS Cloud on AWS EKS?

Follow the blog post guide for AWS EKS, using ofc-bootstrap with AWS Route53 for DNS. You'll need to configure a GitHub App, OAuth, and ensure a public IP and domain name are available for wildcard certificates.

OpenFaaS Cloud vs AWS Lambda for serverless functions?

OpenFaaS Cloud is a self-hosted, multi-tenant platform with GitOps automation, while AWS Lambda is a managed service. Choose OpenFaaS for control, portability, and Kubernetes integration, or AWS Lambda for ease of use and deep AWS ecosystem integration.

Can I use OpenFaaS Cloud with private Git repositories?

Yes, it supports private repositories on GitHub and GitLab through OAuth integration. Configure the GitHub App or GitLab repository tags to grant access, and functions will be built and deployed from private repos.

How to monitor and debug functions in OpenFaaS Cloud?

Use the personal dashboard for runtime logs and build statuses. For advanced monitoring, integrate with external tools via OpenFaaS metrics APIs, as the platform provides immediate feedback but may require additional setup for comprehensive observability.

Is OpenFaaS Cloud suitable for large enterprises?

Yes, with features like multi-user support, HTTPS, and automated CI/CD, but it requires self-hosting and maintenance. Enterprises should consider commercial support from OpenFaaS Ltd for production readiness and scalability.

How to manage secrets in OpenFaaS Cloud functions?

Use the secrets management guide to store sensitive data via Kubernetes secrets or the OpenFaaS Cloud interface. Secrets can be injected at runtime, but ensure proper access controls are configured during setup.

OpenFaaS Cloud

MITGo0.14.4

A multi-user serverless platform that automates CI/CD for functions via git push with GitHub/GitLab integration.

Visit Website

What is OpenFaaS Cloud?

OpenFaaS Cloud is a multi-user, self-hosted serverless platform that automates CI/CD for functions using a GitOps workflow. It integrates with GitHub or GitLab to trigger builds and deployments on git push, providing each user with a personal dashboard to manage and monitor their functions. The platform simplifies serverless operations by eliminating manual deployment steps and reducing tooling requirements.

Target Audience

Development teams and organizations looking to implement a scalable, self-hosted serverless platform with automated CI/CD pipelines. It suits those using Kubernetes and wanting to manage functions through GitOps with GitHub or GitLab integration.

Value Proposition

Developers choose OpenFaaS Cloud for its seamless GitOps automation, multi-user support with personal dashboards, and portability across any cloud. It reduces operational overhead by automating the entire function lifecycle from code push to deployment, while providing enterprise features like HTTPS subdomains and runtime logs.

Overview

The Multi-user OpenFaaS Platform

Use Cases

Best For

Teams wanting automated CI/CD for serverless functions triggered by git push

Related Projects

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

GitHub

770 stars223 forks0 contributors

Organizations needing a multi-tenant serverless platform with user-specific dashboards

Self-hosting a serverless platform on Kubernetes with GitHub or GitLab integration

Implementing GitOps workflows for function deployment and management

Reducing tooling and learning curve for operating serverless functions

Building a portable serverless platform deployable on any cloud infrastructure

Not Ideal For

Teams using source control systems other than GitHub or GitLab
Organizations requiring highly customizable CI/CD pipelines with extensive scripting and branching logic
Projects with minimal serverless function usage that don't justify the overhead of self-hosted platform management
Environments without Kubernetes or access to public cloud infrastructure for deployment

Pros & Cons

Pros

GitOps Automation

Automates the entire CI/CD pipeline from git push to deployment, triggering builds, Docker image creation, registry push, and function deployment as described in the README's workflow.

Multi-User Dashboards

Provides per-user subdomains with HTTPS and personal dashboards for monitoring functions, using GitHub or GitLab identities for authentication and feedback via GitHub Checks or GitLab Statuses.

Portable Self-Hosting

Deployable on any cloud or Kubernetes cluster, offering flexibility and control over infrastructure, as emphasized in the 'Portable' feature and supported by tools like ofc-bootstrap.

Fast, Secure Builds

Utilizes buildkit for non-root Docker image builds, ensuring security and speed in the build process, which is highlighted in the features for reduced operational complexity.

Cons

Complex Initial Setup

Requires detailed knowledge to configure GitHub/GitLab apps, DNS service accounts, and Kubernetes, as noted in the self-hosted deployment instructions needing 'basic knowledge' of these components.

Limited SCM Integration

Only supports GitHub and GitLab, excluding other source control systems like Bitbucket or self-hosted Git servers, which limits adoption for teams using diverse tools.

Self-Hosted Maintenance Overhead

Being self-hosted means organizations must manage all infrastructure, security, and updates, adding operational complexity compared to managed serverless services.

Frequently Asked Questions

Home

Serverless Framework

firecracker

Secure and fast microVMs for serverless computing.

Stars34,097

Forks2,370

Last commit2 days ago

Serverless Framework2.2k