Files
fission-src/fission-cloud.yaml
T
Ta-Ching ChenandSoam Vasani a13015e75a Add function logs support (#53) (#131)
Add function log aggregation and persistence using Fluentd and InfluxDB.

Fluentd and a helper sidecar run as a daemonset.  The poolmgr sets up logging for each function pod, using the helper sidecar. Fluentd forwards logs to InfluxDB, which is run as a deployment and service. The client CLI directly queries InfluxDB for logs.

Fluentd supports many outputs besides InfluxDB, so we aren't very tied to InfluxDB.

The setup is somewhat manual, which we should be able to improve by integrating this into the helm chart.

Diagram of component interactions: https://cloud.githubusercontent.com/assets/202578/23100399/b0e3ea00-f6ba-11e6-8f2f-6588cfef2e84.png
2017-03-22 15:59:42 -07:00

51 lines
810 B
YAML

apiVersion: v1
kind: Service
metadata:
name: router
namespace: fission
labels:
svc: router
spec:
type: LoadBalancer
ports:
- port: 80
targetPort: 8888
nodePort: 31314
selector:
svc: router
---
apiVersion: v1
kind: Service
metadata:
name: controller
namespace: fission
labels:
svc: controller
spec:
type: LoadBalancer
ports:
- port: 80
targetPort: 8888
nodePort: 31313
selector:
svc: controller
---
# If you want to switch to external db service, please checkout
# sample Kubernetes Service config in fission-logger.yaml.
apiVersion: v1
kind: Service
metadata:
name: influxdb
namespace: fission
labels:
svc: influxdb
spec:
type: LoadBalancer
ports:
- port: 8086
targetPort: 8086
nodePort: 31315
selector:
svc: influxdb