- This change points the roadmap back to the documentation and
GitHub issue trackers
- Draws distinction between OF and OFC.
Signed-off-by: Alex Ellis <alexellis2@gmail.com>
- re-vendor queue-worker for publisher via 0.6.0
- bump queue-worker version to 0.6.0 in docker-compose.yml for
AMD64
- use new naming for NATS of nats -> NATS in variables where
required
- add default reconnect of 60 times, 2 seconds apart.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- adds max_idle_conns_* default values to docker-compose.yml to
make it easier to override as a user doing testing/tuning
- make Golang durations easier to read 300s -> 5m
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
**What**
- Bumps the gateway version to 0.10.2 in the default docker-compose file
**Why**
- Finishes the work started in #1049 to enable basic auth for the alert
endpoint, this will allow the deployment via compose to leverage the
basic auth
Signed-off-by: Lucas Roesler <roesler.lucas@gmail.com>
- this caused confusion for a user who had logged in for
"127.0.0.1", but not for "localhost" then saw an error when
deploying and trying to access "localhost" for which there
was no credential available.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
OpenFaaS is covered in the newly publish Serverless book Serverless Inside Out.
Committed by @nichochen
Signed-off-by: Ivana Yovcheva (VMware) <iyovcheva@vmware.com>
This shows the list of backers >= 5 USD from Patreon.com who
contribute and receive a reward-level, a mention in BACKERS.md
and help with the various running-costs of the independent
project.
Signed-off-by: Alex Ellis <alexellis2@gmail.com>
**What**
- Revert to the original docker tags because we want to for the bump
until after the official release
Signed-off-by: Lucas Roesler <roesler.lucas@gmail.com>
**What**
- Protect the `/system/alert` endpoint when basic auth is enabled
- Update the alert manager config to send the basic auth credentials
- Bump the gateway version
Signed-off-by: Lucas Roesler <roesler.lucas@gmail.com>
- the order of http_requests_total was shown to be incorrect in
testing. This fixes the order as per
http_request_duration_seconds.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- according to discussion in #1013 all unicode characters are
valid label values - this commit allows the original path to be
retained.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- instruments async handler for report and for queueing async
requests
- make MustRegister only ever run once to prevent sync issues
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- updates the Prometheus go client version and switches to the
promhttp handler to avoid conflicts with the new system-level
metrics.
Tested with Docker Swarm locally - no conflicts and new metrics
were gathered.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
Partially fixes#532 by introducing two metrics that are
supported by Kubernetes HPAv2 and RED metrics-style
dashboards.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
When the /system/info endpoint was expanded to include information about the gateway a number of build-args were added to the main Dockerfile. These changes were not mirrored in Dockerfile.armhf, which resulted in nil attributes and an ugly error when running `faas version` against an armhf gateway.
This change carries the changes made to Dockerfile through to Dockerfile.armhf. As well as the build-args which fix the identified issue the license check has also been added at the latest release 0.2.3, as a armhf build has been made available. Further changes are to introduce the app user and moving the binary location from /root/ to /home/app/
Signed-off-by: Richard Gee <richard@technologee.co.uk>
Adding blog post about Serverless on Raspberry PI with
Docker Swarm and OpenFaaS by Mathias Deremer in the
Blog posts and write-ups 2019
Signed-off-by: Martin Dekov (VMware) <mdekov@vmware.com>
This change validates manual input to the gateway UI when deploying
new functions. This is to prevent poor user experience when attempting
to deploy a function manually from the UI.
The validation check on the function name is the same pattern that
is used in the CLI to ensure that when the deploy button is pressed,
the function will not fail validation.
Signed-off-by: Burton Rheutan <rheutan7@gmail.com>
