mirror of
https://github.com/fnproject/fn.git
synced 2022-10-28 21:29:17 +03:00
a32ca3d90a
* moving documentation around to be more clear and easier to browse - moved assets into their own directory and updated links to them - moved operating docs into their own directory - consolidated kubernetes docs - added docker-swarm folder for docs - updated docs layout in docs/README.md to reflect the changes and make it easier to read * docs: s/Operating Functions/Operating IronFunctions/ * docs: removing duplicate database link * docs: moving databases into general docs * docs: moving databases/mqs back * docs: removing memory.md (duplicate of operating/routes.md) * docs: converting to markdown bullets
110 lines
4.1 KiB
Markdown
110 lines
4.1 KiB
Markdown
# HOWTO run IronFunction in Kubernetes at AWS
|
|
|
|
*Prerequisite 1: it assumes you have a working Kubernetes, and a locally configured kubectl.*
|
|
|
|
*Prerequisite 2: It assumes you are using Kubernetes 1.4 or newer.*
|
|
|
|
|
|
## Quickstart
|
|
|
|
### Steps
|
|
|
|
1. Start IronFunction in the Kubernetes cluster:
|
|
```ShellSession
|
|
$ cd docs/
|
|
$ kubectl create -f kubernetes-quick
|
|
```
|
|
|
|
2. Once the daemon is started, check where it is listening for connections:
|
|
|
|
```ShellSession
|
|
# kubectl describe svc functions
|
|
|
|
Name: functions
|
|
Namespace: default
|
|
Labels: app=functions
|
|
Selector: app=functions
|
|
Type: LoadBalancer
|
|
IP: 10.0.116.122
|
|
LoadBalancer Ingress: a23122e39900111e681ba0e29b70bb46-630391493.us-east-1.elb.amazonaws.com
|
|
Port: <unset> 8080/TCP
|
|
NodePort: <unset> 30802/TCP
|
|
Endpoints: 10.244.1.12:8080
|
|
Session Affinity: None
|
|
Events:
|
|
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
|
|
--------- -------- ----- ---- ------------- -------- ------ -------
|
|
22m 22m 1 {service-controller } Normal CreatingLoadBalancer Creating load balancer
|
|
22m 22m 1 {service-controller } Normal CreatedLoadBalancer Created load balancer
|
|
|
|
```
|
|
|
|
Note `a23122e39900111e681ba0e29b70bb46-630391493.us-east-1.elb.amazonaws.com` in `LoadBalancer Ingress` line, this is where the service is listening.
|
|
|
|
3. Test the cluster:
|
|
|
|
```ShellSession
|
|
$ export IRON_FUNCTION=$(kubectl get -o json svc functions | jq -r '.status.loadBalancer.ingress[0].hostname'):8080
|
|
|
|
$ curl -H "Content-Type: application/json" -X POST -d '{ "app": { "name":"myapp" } }' http://$IRON_FUNCTION/v1/apps
|
|
{"message":"App successfully created","app":{"name":"myapp","config":null}}
|
|
|
|
$ curl -H "Content-Type: application/json" -X POST -d '{ "route": { "type": "sync", "path":"/hello-sync", "image":"iron/hello" } }' http://$IRON_FUNCTION/v1/apps/myapp/routes
|
|
{"message":"Route successfully created","route":{"appname":"myapp","path":"/hello-sync","image":"iron/hello","memory":128,"type":"sync","config":null}}
|
|
|
|
$ curl -H "Content-Type: application/json" -X POST -d '{ "name":"Johnny" }' http://$IRON_FUNCTION/r/myapp/hello-sync
|
|
Hello Johnny!
|
|
```
|
|
|
|
## Production
|
|
|
|
### Steps
|
|
|
|
1. Start IronFunction and its dependencies:
|
|
```ShellSession
|
|
$ cd docs/
|
|
$ kubectl create -f kubernetes-production
|
|
```
|
|
|
|
*Optionally, you might have both Redis and PostgreSQL started somewhere else, in this case, remember to update kubernetes-production/functions-config.yaml with the appropriate configuration.*
|
|
|
|
2. Once the daemon is started, check where it is listening for connections:
|
|
|
|
```ShellSession
|
|
# kubectl describe svc functions
|
|
|
|
Name: functions
|
|
Namespace: default
|
|
Labels: app=functions
|
|
Selector: app=functions
|
|
Type: LoadBalancer
|
|
IP: 10.0.116.122
|
|
LoadBalancer Ingress: a23122e39900111e681ba0e29b70bb46-630391493.us-east-1.elb.amazonaws.com
|
|
Port: <unset> 8080/TCP
|
|
NodePort: <unset> 30802/TCP
|
|
Endpoints: 10.244.1.12:8080
|
|
Session Affinity: None
|
|
Events:
|
|
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
|
|
--------- -------- ----- ---- ------------- -------- ------ -------
|
|
22m 22m 1 {service-controller } Normal CreatingLoadBalancer Creating load balancer
|
|
22m 22m 1 {service-controller } Normal CreatedLoadBalancer Created load balancer
|
|
|
|
```
|
|
|
|
Note `a23122e39900111e681ba0e29b70bb46-630391493.us-east-1.elb.amazonaws.com` in `LoadBalancer Ingress` line, this is where the service is listening.
|
|
|
|
3. Test the cluster:
|
|
|
|
```ShellSession
|
|
$ export IRON_FUNCTION=$(kubectl get -o json svc functions | jq -r '.status.loadBalancer.ingress[0].hostname'):8080
|
|
|
|
$ curl -H "Content-Type: application/json" -X POST -d '{ "app": { "name":"myapp" } }' http://$IRON_FUNCTION/v1/apps
|
|
{"message":"App successfully created","app":{"name":"myapp","config":null}}
|
|
|
|
$ curl -H "Content-Type: application/json" -X POST -d '{ "route": { "type": "sync", "path":"/hello-sync", "image":"iron/hello" } }' http://$IRON_FUNCTION/v1/apps/myapp/routes
|
|
{"message":"Route successfully created","route":{"appname":"myapp","path":"/hello-sync","image":"iron/hello","memory":128,"type":"sync","config":null}}
|
|
|
|
$ curl -H "Content-Type: application/json" -X POST -d '{ "name":"Johnny" }' http://$IRON_FUNCTION/r/myapp/hello-sync
|
|
Hello Johnny!
|
|
``` |