Skip to content

Commit 9057e56

Browse files
committed
Remove management image
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
1 parent 38be108 commit 9057e56

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

_posts/2024-09-23-meet-openfaas-edge.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -152,10 +152,16 @@ Examples of where OpenFaaS Edge could be used include:
152152
* A local API or appliance for a customer to use locally, or connected to the cloud
153153
* A local processing engine for a SaaS application
154154

155+
### Remote monitoring and support
156+
155157
Monitoring and support can be achieved using the OpenFaaS REST API, with a logging agent to forward logs from the systemd journal to a centralised logging system, and with Prometheus which contains detailed RAM/CPU usage metrics, and [HTTP invocation metrics from the OpenFaaS Pro gateway and JetStream Queue Worker](https://docs.openfaas.com/architecture/metrics/).
156158

157159
For remote access to the OpenFaaS REST API and Prometheus metrics, you can use a solution like our inlets uplink product, which does not require a VPN, firewall rule, or port forwarding. It makes an outbound TLS connection to your Kubernetes cluster. Your internal applications can then interact with the two HTTP endpoints as if they were local within the cluster.
158160

161+
![Inlets Uplink example](/images/2024-09-openfaas-edge/remote-management.png)
162+
163+
> Only services within your own Kubernetes cluster can access each tenant's tunnel. The tunnel can expose multiple HTTP and TCP services, such as Prometheus and OpenFaaS. If you run a Postgresql database via faasd, you could also expose that in the same way.
164+
159165
[Learn about inlets uplink](https://inlets.dev/blog/2022/11/16/service-provider-uplinks.html)
160166

161167
## Q&A
823 KB
Loading

0 commit comments

Comments
 (0)