faasd has always been covered by the OpenFaaS CE EULA, the
presence of the document in the faas repo does not mean it
only applies to a single repository.
faasd is OpenFaaS, they are not different products.
OpenFaaS CE requires a commercial license for use as has been
explained on the website and in the docs.
https://www.openfaas.com/pricinghttps://docs.openfaas.com/openfaas-pro/introduction/#comparison
This EULA Addendum permits explit personal usage and small
business environments to commercial usage of faasd only, with
OpenFaaS CE, but does not cover OpenFaaS CE deployed to
Kubernetes or K3s, or OpenShift.
For questions or comments, reach out to contact@openfaas.com
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
Whilst the ROADMAP was already linked, one user was confused
about the design decisions of faasd, so this adds a second
link to make it more likely he would click on it in the future.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
Pin scripts and automation to the latest version of faasd
which moves to use the openfaas namespace for the core
services instead of default.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
All services like docker and k8s.io use their own namespaces
for core services, this change moves openfaas services into
the openfaas namespace instead of the default one.
The main change is that logs will look like:
journalctl -t openfaas:gateway
Instead of "default:gateway"
Function logs will remain unaffected and scheduled in the
openfaas-fn namespace.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
Memory limits now work and a function will be killed with OOM
however, it will remain in a stopped state and will not
restart automatically.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
