You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenFaaS Standard and OpenFaaS for Enterprises are licensed for use within an airgap when purchased on an annual basis via invoice.
4
+
5
+
You can use your own choice of tooling to mirror images and bundle the Helm chart(s) required for your installations, or you can use our own purpose-built airfaas tool.
6
+
7
+
### Mirror OpenFaaS images into your own registry
8
+
9
+
If your organisation has a policy of mirroring all consumed images from vendors into a private registry, then `airfaas mirror` can help you with this, even if you don't install OpenFaaS into an airgapped environment.
10
+
11
+
```bash
12
+
faas-cli plugin get airfaas
13
+
```
14
+
15
+
Mirror all images for the given chart/index to a custom registry:
16
+
17
+
```bash
18
+
airfaas download images \
19
+
openfaas/openfaas \
20
+
--registry-prefix ttl.sh
21
+
```
22
+
23
+
Mirror the Kafka-connector's images:
24
+
25
+
```bash
26
+
airfaas download images \
27
+
openfaas/kafka-connector \
28
+
--registry-prefix ttl.sh
29
+
```
30
+
31
+
The `--url` flag can be used to specify a different Helm chart repository. The only requirement is that images are stored in the same format as OpenFaaS: i.e. `image:` or `componentName.image:`.
32
+
33
+
After the mirroring is complete, you'll receive output in the format of a values.yaml file, which you can add to your `helm upgrade --install` command.
Your final OpenFaaS Pro installation may look something like, where you use the standard `values-pro.yaml` file, your own settings in `values-staging.yaml`, then finally the mirrored images overlaid over that in `values-mirror.yaml`:
52
+
53
+
```bash
54
+
helm upgrade --install openfaas \
55
+
--install openfaas/openfaas \
56
+
--namespace openfaas \
57
+
-f values-pro.yaml \
58
+
-f values-staging.yaml \
59
+
-f values-mirror.yaml
60
+
```
61
+
62
+
### Perform an offline installation
63
+
64
+
Airfaas can perform an offline installation of OpenFaaS into an airgapped environment. It will bundle the Helm chart(s) and images required for the installation, then restore the images into an offline registry, and install OpenFaaS using the Helm chart(s) from the local filesystem.
Copy file name to clipboardExpand all lines: docs/openfaas-pro/introduction.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Efficiency and redundancy:
18
18
*[Scale idle functions to zero](/openfaas-pro/scale-to-zero) to save on compute costs, increase efficiency and lower your threat profile
19
19
*[Retry failed invocations for functions](/openfaas-pro/retries) to handle issues with downstream APIs and back-pressure on concurrency-limited functions
20
20
* CPU and RAM usage metrics for every function to measure usage and fine-tune limits
21
-
* GitOps compatibility with the Function CustomResource, with Helm, ArgoCD and FluxCD.
21
+
*[GitOps compatibility with the Function CustomResource, with Helm, ArgoCD and FluxCD](/openfaas-pro/function-crd)
22
22
23
23
[](/architecture/autoscaling/)
24
24
> Scaling that works for various types of functions
@@ -38,7 +38,8 @@ The OpenFaaS dashboard integrates with CPU & RAM usage metrics, and container lo
38
38
Event-driven programming and triggers:
39
39
40
40
*[Trigger functions via Kafka](/openfaas-pro/kafka-events) for event-driven functions and to integrate with your existing systems
41
-
*[Trigger functions from AWS SQS](/openfaas-pro/sqs-events) to integrate with events from AWS.
41
+
*[Trigger functions from AWS SQS](/openfaas-pro/sqs-events) to integrate with events from AWS services via a managed queue.
42
+
*[Trigger functions from AWS SNS](/openfaas-pro/sns-events) to integrate with events from AWS managed services via pub/sub.
42
43
43
44
### Workload tuning
44
45
@@ -50,14 +51,15 @@ To avoid errors when scaling up or down, you may need to tune your function's co
50
51
* Custom TerminationGracePeriod for draining work for long running functions
51
52
* Custom support for probing Istio endpoints during scale from zero
52
53
53
-
Read more: [OpenFaaS workloads](https://docs.openfaas.com/reference/workloads/) and [Custom Profiles](https://docs.openfaas.com/reference/profiles/#use-an-alternative-runtimeclass)
54
+
Read more: [OpenFaaS workloads](/reference/workloads/) and [OpenFaaS Profiles](/reference/profiles/#use-an-alternative-runtimeclass)
54
55
55
56
### Enterprise security
56
57
57
-
* Identity and Access Management (IAM)
58
-
* Single Sign On with OpenID Connect (OIDC)
58
+
*[Airgapped/offline installations and image mirroring](/openfaas-pro/airgap)
59
+
*[Identity and Access Management (IAM)](/openfaas-pro/iam/overview)
60
+
*[Single Sign On with OpenID Connect (OIDC)](/openfaas-pro/sso/overview)
59
61
60
-
[Learn more about IAM for OpenFaaS](https://docs.openfaas.com/openfaas-pro/iam/overview/)
62
+
[Learn more about IAM for OpenFaaS](/openfaas-pro/iam/overview)
61
63
62
64
### Platform building features
63
65
@@ -112,10 +114,9 @@ Recently released:
112
114
* GPU scheduling support for functions via Profiles i.e. `nvidia.com/gpu: 1` (Mar 2024)
113
115
114
116
Upcoming:
115
-
117
+
* Built-in function authentication with IAM for OpenFaaS (in preview)
116
118
* Conversion to structured/JSON logging of OpenFaaS Pro components (ongoing - 80% complete)
117
119
* Dynamic, dedicated Async queues for each function, including queued-based scaling (R&D phase)
118
-
* Function authentication with IAM for OpenFaaS
119
120
* Go SDK for the Function Builder API
120
121
* Additional event triggers i.e. AMQP event trigger for RabbitMQ and Azure Service Bus and Google PubSub (added upon request)
121
122
@@ -127,14 +128,12 @@ If you're already a customer, we welcome suggestions for the roadmap in [the Cus
127
128
128
129
!!! info "Do we need the Community Edition or Pro?"
129
130
130
-
OpenFaaS Community Edition (CE) is meant for open-source developers and initial exploration of functions, OpenFaaS Pro is meant for production.
131
+
OpenFaaS Community Edition (CE) is licensed for open-source developers and initial exploration of functions, OpenFaaS Pro is licensed for production.
131
132
132
133
OpenFaaS Pro is a distribution of OpenFaaS with additional features and configurations that we believe customers need to operate a product or service in production.
133
134
134
135
As we tune OpenFaaS Pro for our existing customers, we improve it for everyone else at the same time - writing articles, tuning configuration and adding key features.
135
136
136
-
We see it as the start of a two-way relationship and an opportunity to collaborate directly with our team.
137
-
138
137
**Support**
139
138
140
139
All the items below are included in the standard self-service/license-only package, unless specifically stated as requiring an Enterprise Service Agreement.
0 commit comments