fission/fission-charts

Repo for fission charts

Fission: Serverless Functions for Kubernetes

---

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

• Table of Contents
  • Performance: 100msec cold start
  • Kubernetes is the right place for Serverless
  • Getting Started
  • Learn More
  • Contributing
  • Who is using Fission?
  • Sponsors
• License

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.
• To see Fission in action, check out the Fission Examples Repo.
• See the troubleshooting guide for debugging your functions and Fission installation.

Contributing

Check out the contributing guide.

Who is using Fission?

• Fareye
• Apple
• iQuanti
• A large telecom CSP
• Gadget
• CinnamonAI
• Armo
• The Social Audience
• KubeML
• Unilever
• BD
• Biofourmis
• Babylon

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.

License

Fission is licensed under the Apache License 2.0 - see the LICENSE file for details

fission-charts's Issues

extraCoreComponentPodConfig nesting error in deployment-template

templates/deployment.yaml contains the following block at line 697:

---
{{- if .Values.kafka.authentication.tls.enabled }}
...
{{- end }}
{{- if .Values.extraCoreComponentPodConfig }}
{{ toYaml .Values.extraCoreComponentPodConfig | indent 6 -}}
{{- end }}

which leads to the generation of a single extraCoreComponentPodConfig-block after rendering the template whenever it is defined. I'm quite sure the extraCoreComponentPodConfig-block should be inside the kafka.authentication.tls.enabled-block above.

---

For example if my values-file contains this:

extraCoreComponentPodConfig:
  tolerations:
  - key: faas
    operator: Exists
    effect: NoSchedule

the rendered template will contain this:

---
# Source: fission-all/templates/deployment.yaml
tolerations:
      - effect: NoSchedule
        key: faas
        operator: Exists
---

which obviously isn't a valid kubernetes-object.

Tested in fission-all-1.12.0

debugEnv flag support

debugEnv flag is not supported for an executor in the Fission core helm chart, but it is available in the Fission all helm chart (v1.14.1).

It should be available in all installations.

Fission Charts and Repository Enhancements

We would be closely following prometheus-community/helm-charts as a reference and taking Fission charts repo towards those standards.
 

Steps

1. Add detailed README in fission-charts Repo
2. Add README in each chart, it is required for Artifact Hub official releases. This is required to improve user exp and make our charts official on Artifact Hub.
3. Switch default branch to gh-pages from master in charts repo to serve charts Reference
4. Migrated Fission charts source from Fission repository to charts repository, ensure no failures
5. Reduction of common code between fission-all and fission-core helm charts and common templates.
6. Separate charts release and Fission images/app release. This would require further breakdown going ahead.
7. Use chart-releaser-action for releasing charts
8. Use chart-testing for testing of charts, add unit tests

Contributor Notes

• We should ensure there should be clear migration/usage steps mentioned for Fission users.
• All required documentation should be prepared alongside the code.
• We can treat this as a parent issue and link other issues as required.

unable to pass values into helm chart on install

➜ helm install --version v1.19.0 --namespace $FISSION_NAMESPACE fission fission-charts/fission-all --values fission-values.yaml 

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: Namespace "fission" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "fission"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "fission"

fission-values.yaml:

defaultNamespace: fission
builderNamespace: fission
functionNamespace: fission
additionalFissionNamespaces:
  - prod