Previous Spec was flawed as it showed that the response model was
```
[
{
"name": "aws-key",
"value": "changeme"
}
]
```
Changed the model to match what is returned
Signed-off-by: Rishabh Gupta<r.g.gupta@outlook.com>
**What**
- Removes the `alert` label in the scale-up alert
- Updates the annotaitons to use the `function_name` label instead of
the `instance` label that was removed.
- Per prometheus/prometheus#4836 and the related mailing list discussion
https://groups.google.com/d/msg/prometheus-users/7Ul6ngc7Ogs/j_YDszV5BwAJ
the alert value should not be included in the alert labels otherwise
each calculation of the alert is treated like a new alert and then the
use of `for 5s` will not behave as expected.
- Ports the resoltuion openfaas/faas-netes#372
Signed-off-by: Lucas Roesler <roesler.lucas@gmail.com>
Adding blog post by Richard Gee in the official
openfaas site with title RIde the SErverless Wave with
DigitalOcean's One-click Droplet
Signed-off-by: Martin Dekov (VMware) <mdekov@vmware.com>
- max_conns / idle / per host are now read from env-vars and have
defaults set to 1024 for both values
- logging / metrics are collected in the client transaction
rather than via defer (this may impact throughput)
- function cache moved to use RWMutex to try to improve latency
around locking when updating cache
- logging message added to show latency in running GetReplicas
because this was observed to increase in a linear fashion under
high concurrency
- changes tested against 3-node bare-metal 1.13 K8s cluster
with kubeadm
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- due to what appears to be a frequent issue with the Go HTTP
client some tweaks were needed to the HTTP client used for
reverse proxying to prevent CoreDNS from rejecting connections.
The following PRs / commits implement similar changes in
Prometheus and Minio.
https://github.com/prometheus/prometheus/pull/3592https://github.com/minio/minio/pull/5860
Under a 3-node (1-master) kubeadm cluster running on bare
metal with Ubuntu 18.04 I was able to send 100k requests
with 1000 being concurrent with no errors being returned
by hey.
```
hey -n 100000 -c 1000 -m=POST -d="hi" \
http://192.168.0.26:31112/function/go-echo
```
The go-echo function is based upon the golang-http
template in the function store using the of-watchdog.
Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>
- 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>
