Skip to content

Tags: Lambda-NIC/faas-netes

Tags

0.6.4

Toggle 0.6.4's commit message
Bump golang to 1.10.x and alpine to 3.8

**What**
- Bump the base docker image to golang:1.10
- Bump the alpine version to 3.8

Signed-off-by: Lucas Roesler <[email protected]>

0.6.3

Toggle 0.6.3's commit message
Update status code for CRUD APIs

This commit updates the status code from 200 to 202 for create, update
or delete APIs.

Fixes: openfaas#220

Signed-off-by: Vivek Singh <[email protected]>

0.6.2

Toggle 0.6.2's commit message
Expand verbs allowed for proxying

- Adds additional verbs as per g/w and watchdog

Signed-off-by: Alex Ellis (VMware) <[email protected]>

0.6.1

Toggle 0.6.1's commit message
Chart version bumped to 1.2.3

- 1.2.3 version moves the gateway to 0.9.1

Signed-off-by: Alex Ellis (VMware) <[email protected]>

0.6.0

Toggle 0.6.0's commit message
Add annotation support

Store stack.yml annotation meta data in deployment, pod, service and
replicaset

Relates to openfaas/faas#682

Signed-off-by: Edward Wilde <[email protected]>

0.5.7

Toggle 0.5.7's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Correct error in CI

The "latest-dev" tag was specified when it did not exist.

Signed-off-by: Alex Ellis <[email protected]>

0.5.6

Toggle 0.5.6's commit message
Push image to both Quay.io and Docker Hub

With this change faas-netesd will be pushed to Quay.io
on release as a backup

Signed-off-by: Ivana Yovcheva (VMware) <[email protected]>

0.5.5

Toggle 0.5.5's commit message
Bump gw/faas-netes + fix label update

Now that we have a label selector which is distinct from our own
labels we have to update the deployment labels in the update code.

Bumps GW to 0.8.2 (basic auth support) and faas-netesd to latest
for label enhancements. Tested on GKE 1.9.6.

Signed-off-by: Alex Ellis (VMware) <[email protected]>

0.5.4

Toggle 0.5.4's commit message
Move label query to deployment.labels

When querying labels we were returning the selector labels instead
of the deployment labels. This change corrects the regression
which was introduced in 0.5.3.

Signed-off-by: Alex Ellis (VMware) <[email protected]>

0.5.3

Toggle 0.5.3's commit message
Add Selector for deployment

A bug was found where updating through OpenFaaS-Cloud without a
faas_function label was causing an error with the buildshiprun
function. The label selector is required so we have an implicit
match and do not allow K8s to assume we want to match on all labels
because when it does - that means we can't change those labels in
an update.

Tested on kubeadm 1.9.6.

Signed-off-by: Alex Ellis (VMware) <[email protected]>