Currently only some of the deployment of OFC can be done using helm. We still rely on cloning this repo, applying overrides to the openfaas functions yaml files and env variables files.
We could implement the same functionality in the helm chart (with the same config options in the ofc-bootstrap tool) and slowly phase out the need to clone this repo in ofc-bootstrap deployment.
This could be done 1 function at a time into the chart, then changing ofc-bootstrap to apply the new options and not deploy the specific function from the openfaas functions yaml.
This would make OFC components installable with a single helm install command and without needing to port forward to the cluster gateway, login and use faas-cli to deploy.
We should still keep the functions yaml for building and pushing the functions.
Expected Behaviour
All ofc functions and components deployed via helm chart
Current Behaviour
the helm chart implements some of the component deployment, there is still some deployed using faas-cli
Possible Solution
One function at a time moved into the helm chart, possibly deployed behind a flag like core.github-event.enabled=true to enable deployment in the chart so it can be slowly introduced into the automation tooling.
Context
The ofc-bootstrap tool needs to download this repo, template over files, then connect to the of gateway as well as install some components using helm. Implementing all functionality in helm would allow us to remove some complexity from the ofc-bootstrap tool and make it quicker to install (no need to download this repo if we are using helm only)
Currently only some of the deployment of OFC can be done using helm. We still rely on cloning this repo, applying overrides to the openfaas functions yaml files and env variables files.
We could implement the same functionality in the helm chart (with the same config options in the ofc-bootstrap tool) and slowly phase out the need to clone this repo in ofc-bootstrap deployment.
This could be done 1 function at a time into the chart, then changing ofc-bootstrap to apply the new options and not deploy the specific function from the openfaas functions yaml.
This would make OFC components installable with a single helm install command and without needing to port forward to the cluster gateway, login and use faas-cli to deploy.
We should still keep the functions yaml for building and pushing the functions.
Expected Behaviour
All ofc functions and components deployed via helm chart
Current Behaviour
the helm chart implements some of the component deployment, there is still some deployed using faas-cli
Possible Solution
One function at a time moved into the helm chart, possibly deployed behind a flag like
core.github-event.enabled=trueto enable deployment in the chart so it can be slowly introduced into the automation tooling.Context
The ofc-bootstrap tool needs to download this repo, template over files, then connect to the of gateway as well as install some components using helm. Implementing all functionality in helm would allow us to remove some complexity from the ofc-bootstrap tool and make it quicker to install (no need to download this repo if we are using helm only)