mirror of
https://github.com/serverless/serverless.git
synced 2026-01-25 15:07:39 +00:00
Merge pull request #6721 from vognev/docs/kubeless-url-zip
documented url+zip deploy strategy for serverless-kubeless
This commit is contained in:
commit
163fa830cf
@ -77,6 +77,27 @@ rs/hello-699783077 1 1 1 2m
|
||||
|
||||
Kubeless will create a [Kubernetes Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) for your function and a [Kubernetes service](https://kubernetes.io/docs/concepts/services-networking/service/) for each event.
|
||||
|
||||
Deployment will spin up a [Pod](https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/)) based on runtime you have defined in your `serverless.yml`. Runtime is a public docker image, providing only binaries for your code. Function code itself is injected into Pod by `kubeless-controller-manager` and stored in Kubernetes Function object definition.
|
||||
|
||||
Kubernetes Function definition has a size limit, since it is stored as yaml in cluster's etcd. So, you can't deploy function any larger than approximately 1.5MB.
|
||||
|
||||
In order to overcome this limitation, function code can be fetched from [external url](https://kubeless.io/docs/advanced-function-deployment/); in this case only link (and checksum) is stored in Kubernetes function definition. Starting from v0.8.0 of `serverless-kubeless`, you can change default deployment method to `S3ZipContent` and configure `serverless-kubeless` with S3 bucket, where the function code will be stored:
|
||||
|
||||
```yaml
|
||||
provider:
|
||||
name: kubeless
|
||||
runtime: python2.7
|
||||
deploy:
|
||||
strategy: S3ZipContent
|
||||
options:
|
||||
accessKeyId: minio
|
||||
secretAccessKey: minio123
|
||||
endpoint: http://minio.local
|
||||
bucket: workbench
|
||||
region: eu-central-1
|
||||
s3ForcePathStyle: True
|
||||
```
|
||||
|
||||
## Deploy Function
|
||||
|
||||
This deployment method updates or deploys a single function. It performs the platform API call to deploy your package without the other resources. It is much faster than redeploying your whole service each time.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user