deploy fail on kubernetes: kubectl apply fail

[openfaas]

deploy fail on kubernetes: kubectl apply fail

[rayhero]

After I use helm to delete old service account. I can install it using Helm.
But when I try to run the faas-cli sample, it says I not deploy Faas. the error is show below:

Error removing existing function: Delete http://localhost:8080/system/functions: dial tcp [::1]:8080: getsockopt: connection refused, gateway=http://localhost:8080, functionName=url-ping
Is FaaS deployed? Do you need to specify the --gateway flag?
Post http://localhost:8080/system/functions: dial tcp [::1]:8080: getsockopt: connection refused

[lizrice]

I just hit exactly this issue trying to apply the helm chart on minikube. Applying the ClusterRole from the YAML file @stefanprodan supplied in #74 fixed it i.e. I created a YAML file with that ClusterRole, applied that file and then the helm installation worked fine.

[alexellis]

What are you using? minikube?

[alexellis]

@weikinhuang can you advise? Maybe if this is minikube rbac.yml shouldn't be applied?

[rayhero]

I install the minikube for testing. But I want to deploy faas-netes on GKE. So I change kubectl config settings to set current-context to GKE cluster. Do I miss some setting so faas-netes still try to deploy on minikube?

[rayhero]

What's the cluster master version could run this project? My GKE current master version is 1.7.6-gke.1. Does this effect the deploy result?

[rayhero]

I downgrade version to 1.6.10-gke.1 but still meet the same problem. Does anyone has experience in deploying this project on GKE?

[alexellis]

Yes @rawkode installed on GKE. Have you tried installing with Helm and RBAC?

[rayhero]

I try to use Helm to deploy, but still meet other problem:
`helm upgrade --install --debug --reset-values --set async=false --set rbac=false openfaas openfaas/
[debug] Created tunnel using local port: '55702'

[debug] SERVER: "localhost:55702"

Release "openfaas" does not exist. Installing it now.
[debug] CHART PATH: /Users/chenszuwei/AutoHotSpot/FAAS/faas-netes/openfaas

Error: release openfaas failed: serviceaccounts "faas-controller" already exists`

why I get this error? Can I remove faas-comntroller??

[weikinhuang]

Helm won't install the chart without a force flag if existing resources with the same name already exists

[rawkode]

@rayhero Use port-forward to get the Gateway available locally and run again

[zouyee]

First,please exec ns -lptn|grep 8080 to confirm port opened
Second, exec sysctl -a|grep net.ipv4.ip_forward must be net.ipv4.ip_forward = 1
Third, checkout service.

[allamand]

I've got same problem when deploying on GKE with kubectl without any modification fo stacks file from the repo. Do I have to change anything so that it can works on GKE ?

Error from server (Forbidden): error when creating "rbac.yml": clusterroles.rbac.authorization.k8s.io "faas-controller" is forbidden: attempt to grant extra privileges

thanks

[alexellis]

Have a look at this from @stefanprodan

#74

[allamand]

Following the steps from @stefanprodan works for me, deployed with kubectl. Thanks

[skunkwerk]

I'm running into this issue trying to deploy to GKE. The link to the YAML file in #74 goes to a 404. Could someone please provide workable installation instructions for non-RBAC Kubernetes?

[alexellis]

Just curious why you aren't using RBAC @skunkwerk? The helm chart should work for you? It has an option to turn off rbac

[alexellis]

I am updating the YAML files for the standard installation method in the yaml branch - #105

[alexellis]

Closing issue due to inactivity. Please feel free to keep commenting - it's very important to us that this works for everyone.

[fergalmoran]

I have a similar issue (I think) - trying to install the samples. This is on ARM (I have created the openfaas namespaces).

kubectl apply -f samples.yml

Deploying: ruby-echo.                                                     
Server returned unexpected status code 500 deployments.extensions "ruby-echo" is forbidden: User "system:serviceaccount:default:faas-controller" cannot get deployments.extensions in the namespace "default"

Unexpected status: 500, message: deployments.extensions is forbidden: User "system:serviceaccount:default:faas-controller" cannot create deployments.extensions in the namespace "default"

$ uname -a
Linux kube-master 4.4.50-hypriotos-v7+ #1 SMP PREEMPT Sun Mar 19 14:11:54 UTC 2017 armv7l GNU/Linux

[alexellis]

Hi @fergalmoran I didn't see you commented after the thread was closed. I've re-created the ARMHF YAML files so you should not have any issues with these now.

Just run this and open a new issue if you need to:

kubectl apply -f ./namespaces.yml,./yaml_armhf

[alexellis]

Derek lock: issue resolved