Fission Workflows -> 0.2.0

INSTALL.md

@@ -4,36 +4,36 @@ This document covers the installation of Fission Workflows.
 
 ### Prerequisites
 
-Fission Workflows requires the following to be installed on the host machine:
+Fission Workflows requires the following to be installed on your host machine:
 
 - [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
 - [helm](https://github.com/kubernetes/helm)
 
-Additionally, Fission Workflows requires a
-[Fission](https://github.com/fission/fission) deployment on your
-Kubernetes cluster.  If you do not have a Fission deployment, follow
-[Fission's installation guide](http://fission.io/docs/0.3.0/install/).
+Additionally, Fission Workflows requires a [Fission](https://github.com/fission/fission) 
+deployment on your Kubernetes cluster. If you do not have a Fission deployment, follow
+[Fission's installation guide](http://fission.io/docs/0.4.0/install/).
 
-(Note that Fission Workflows requires Fission 0.3.0 or higher.)
+**(Note that Fission Workflows requires Fission 0.4.1 or higher, with the NATS component installed!)**
 
 ### Installing Fission Workflows
 
 Fission Workflows is an add-on to Fission. You can install both
-Fission and Workflows using helm charts.
+Fission and Fission Workflows using helm charts.
 
 Assuming you have a Kubernetes cluster, run the following commands:
 
 ```bash
-
 # Add the Fission charts repo
 helm repo add fission-charts https://fission.github.io/fission-charts/
 helm repo update
 
-# Install Fission (if you do not have a Fission deployment yet)
-helm install --namespace fission --set serviceType=NodePort -n fission-all fission-charts/fission-all --version 0.3.0
+# Install Fission 
+# This assumes that you do not have a Fission deployment yet, and are installing on a standard Minikube deployment.
+# Otherwise see http://fission.io/docs/0.4.0/install/ for more detailed instructions
+helm install --wait -n fission-all --namespace fission --set serviceType=NodePort --set analytics=false fission-charts/fission-all --version 0.4.1
 
 # Install Fission Workflows
-helm install fission-charts/fission-workflows
+helm install --wait -n fission-workflows fission-charts/fission-workflows --version 0.2.0
 ```
 
 ### Creating your first workflow
@@ -63,5 +63,5 @@ fission route create --method GET --url /fortunewhale --function fortunewhale
 #
 # Invoke the workflow with an HTTP request:
 #
-curl $FISSION_ROUTER/fortunewhale
+curl ${FISSION_ROUTER}/fortunewhale
 ``` 

charts/fission-workflows/Chart.yaml

@@ -1,14 +1,15 @@
 apiVersion: v1
 name: fission-workflows
-version: 0.1.3
-appVersion: 0.1.3
+version: 0.2.0
+appVersion: 0.2.0
 description: Fission Workflows is a fast workflow engine for serverless functions on Kubernetes
 keywords:
 - fission
 - serverless
 - workflows
 - coordination
 - orchestration
+- function-as-a-service
 home: http://fission.io/
 sources:
   - https://github.com/fission/fission-workflows

charts/fission-workflows/templates/deployment.yaml

@@ -1,3 +1,4 @@
+# Workflow Apiserver is an optional component that allows users to query the workflows API through the Fission apiserver.
 {{ if .Values.apiserver }}
 apiVersion: extensions/v1beta1
 kind: Deployment
@@ -18,7 +19,7 @@ spec:
         imagePullPolicy: {{ .Values.pullPolicy }}
         command: ["/fission-workflows-bundle"]
         args: [
-        # Only run apiserver components
+        # Only run components related to accessing the API
           "--nats",
           "--api-http",
           "--api-workflow-invocation",
@@ -35,10 +36,12 @@ spec:
         - name: FNENV_FISSION_CONTROLLER
           value: "{{ .Values.fnenv.fission.controller }}.{{ .Values.fnenv.fission.ns }}"
 ---
+# TODO remove this service once all functionality is accessible through Fission
 apiVersion: v1
 kind: Service
 metadata:
   name: workflows-apiserver
+  namespace: {{ .Release.Namespace }}
   labels:
     svc: workflows-apiserver
     chart: "{{ .Chart.Name }}-{{ .Chart.Version }}"
@@ -51,7 +54,7 @@ spec:
     svc: workflows-apiserver
 ---
 {{ end }}
-# Workflow Engine is managed like any other environment in Fission
+# Workflow Engine is deployed as just another Fission environment.
 apiVersion: fission.io/v1
 kind: Environment
 metadata:
@@ -62,13 +65,13 @@ spec:
   runtime:
     image: "{{ .Values.envImage }}:{{.Values.tag}}"
     env:
-    - name: "ES_NATS_URL"
+    - name: ES_NATS_URL
       value: "nats://{{ .Values.nats.authToken }}@{{ .Values.nats.location }}.{{ .Values.fnenv.fission.ns }}:{{ .Values.nats.port }}"
-    - name: "ES_NATS_CLUSTER"
+    - name: ES_NATS_CLUSTER
       value: "{{ .Values.nats.cluster }}"
-    - name: "FNENV_FISSION_CONTROLLER"
+    - name: FNENV_FISSION_CONTROLLER
       value: "{{ .Values.fnenv.fission.controller }}.{{ .Values.fnenv.fission.ns }}"
-    - name: "FNENV_FISSION_EXECUTOR"
+    - name: FNENV_FISSION_EXECUTOR
       value: "{{ .Values.fnenv.fission.executor }}.{{ .Values.fnenv.fission.ns }}"
   builder:
     image: "{{ .Values.buildEnvImage }}:{{.Values.tag}}"

charts/fission-workflows/values.yaml

@@ -11,7 +11,7 @@ envImage: fission/workflow-env
 # Image of the Fission build environment for Fission Workflows
 buildEnvImage: fission/workflow-build-env
 
-tag: 0.1.3
+tag: 0.2.0
 
 pullPolicy: IfNotPresent
 

pkg/version/version.go

@@ -1,3 +1,3 @@
 package version
 
-const VERSION = "0.1.3"
+const VERSION = "0.2.0"