5b1883802e
* Adding upgrade workflow file * Update upgrade_test.yaml * Update push_pr.yaml * Update upgrade_test.yaml * adding kube A * Update upgrade_test.yaml * adding script for upgrade testing * adding fission cli from soource * changing order * correcting typo * adding fission fn * restructirung upgrade test scripts * restructirung upgrade test scripts * adding fission cli build * script arrangment * script arrangment * changing job name * adding supporting scripts * adding supporting scripts * adding supporting scripts * script re-ordered * script re-ordered * script modifcation * moved scripts under /test * separated function test blocks * added a sleep * reverting main workflow changes * added stable version installation step * added stable version installation step * stable fn test * adding latest version build * adding latest version build * adding new tests * adding new tests * adding new tests * adding new tests * adding new tests * adding new tests * adding new tests * adding new tests * adding new stable release * adding new stable release * disabling skaffold build and using docker build * disabling skaffold build and using docker build * disabling skaffold build and using docker build * disabling skaffold build and using docker build * fission upgrade using helm * fission upgrade using helm * fission upgrade using helm * fission upgrade using helm * fission upgrade using helm * fission upgrade using helm * fission upgrade using helm * fission upgrade using helm * adding helm upgrade with dependency update * cleanup scripts * added crd deletion step before helm upgrade * added crd deletion step before helm upgrade * added crd deletion step before helm upgrade * adding run tests * added test apache deployment * change in repo name * helm list added * changed pullpolicy * troubleshooting * troubleshooting * troubleshooting * troubleshooting * troubleshooting * troubleshooting * removed hardcoded enteries from helm charts * fixing alignment * cleanup * cleanup * cleanup * cleanup * cleanup * removed temp files [cleanup] * removed timeout * adding preupgradechecks image build * adding fission object creation after upgrade * removing fissin object creation after upgrading... * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * workflow step split-up * clean-up * clean-up * output formatting * added a sleep to re-create resources * added a sleep to re-create resources * added a sleep to re-create resources * excluded examples from upgrade work flow * removed helm stable update step from workflow * removed helm stable update step from workflow * added pr corrections * typo correction * troubleshooting * troubleshooting * troubleshooting * pr corrections * pr corrections * pr corrections * removed sleep after helm upgrade * fixing typo * remvoed sleep after fn creation * clean-up * clean-up * added workflow_dispatch * added workflow_dispatch * added workflow_dispatch * added workflow_dispatch Co-authored-by: Jithindevasia <jithindevasia@Infraclouds-MacBook-Pro.local> Co-authored-by: Sanket Sudake <sanketsudake@gmail.com>
Fission: Serverless Functions for Kubernetes
fission.io | @fissionio | Slack
Fission is a fast serverless framework for Kubernetes with a focus on developer productivity and high performance.
Fission operates on just the code: Docker and Kubernetes are abstracted away under normal operation, though you can use both to extend Fission if you want to.
Fission is extensible to any language; the core is written in Go, and language-specific parts are isolated in something called environments (more below). Fission currently supports NodeJS, Python, Ruby, Go, PHP, Bash, and any Linux executable, with more languages coming soon.
Table of Contents
Performance: 100msec cold start
Fission maintains a pool of "warm" containers that each contain a small dynamic loader. When a function is first called, i.e. "cold-started", a running container is chosen and the function is loaded. This pool is what makes Fission fast: cold-start latencies are typically about 100msec.
Kubernetes is the right place for Serverless
We're built on Kubernetes because we think any non-trivial app will use a combination of serverless functions and more conventional microservices, and Kubernetes is a great framework to bring these together seamlessly.
Building on Kubernetes also means that anything you do for operations on your Kubernetes cluster — such as monitoring or log aggregation — also helps with ops on your Fission deployment.
Getting Started
# Add the stock NodeJS env to your Fission deployment
$ fission env create --name nodejs --image fission/node-env
# Create a function with a javascript one-liner that prints "hello world"
$ fission function create --name hello --env nodejs --code https://raw.githubusercontent.com/fission/examples/master/nodejs/hello.js
# Run the function. This takes about 100msec the first time.
$ fission function test --name hello
Hello, world!
Learn More
- Understand Fission Concepts.
- See the installation guide for installing and running Fission.
- You can learn more about Fission and get started from Fission Docs.
- See the troubleshooting guide for debugging your functions and Fission installation.
Contributing
Check out the contributing guide.
Get Help & Community Meeting
Fission is a project by many contributors. Reach us on slack or twitter.
A regular community meeting takes place every other Thursday at 09:00 AM PT (Pacific Time). Convert to your local timezone.
Meeting Link: https://zoom.us/j/413921817
The meeting agenda for next meeting and notes from past meetings are maintained in this document. You are welcome to join to discuss direction of project, design and implementation reviews and general questions about project etc.
Official Releases
Official releases of Fission can be found on the releases page. Please note that it is strongly recommended that you use official releases of Fission, as unreleased versions from the master branch are subject to changes and incompatibilities that will not be supported in the official releases.
Sponsors
The following companies, organizations, and individuals support Fission's ongoing maintenance and development. If you are using/contributing to Fission, we would be happy to list you here, please raise a Pull request.
Licensing
Fission is under the Apache 2.0 license.