Skip to content

Instantly share code, notes, and snippets.

@filipproch

filipproch/run_apply.log

Created December 22, 2019 18:00
Show Gist options
  • Save filipproch/a8026157bd54d642468a31cbfca092ea to your computer and use it in GitHub Desktop.
Save filipproch/a8026157bd54d642468a31cbfca092ea to your computer and use it in GitHub Desktop.
Download ZIP
Raw
run_apply.log
2019/12/22 18:55:56 Validating tools available in PATH
exec: kubectl version --client
res: Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T23:42:50Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"darwin/amd64"}
exec: openssl version
res: LibreSSL 2.8.3
exec: helm version -c
res: Client: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
exec: faas-cli version
res:  ___ _____ ____
/ _ \ _ __ ___ _ __ | ___|_ _ __ _/ ___|
| | | | '_ \ / _ \ '_ \| |_ / _` |/ _` \___ \
| |_| | |_) | __/ | | | _| (_| | (_| |___) |
\___/| .__/ \___|_| |_|_| \__,_|\__,_|____/
|_|
CLI:
commit: 73004c23e5a4d3fdb7352f953247473477477a64
version: 0.11.3
Plan loaded from: second.init.yaml
Validating registry credentials fileerror with registry credentials file. Please ensure it has been created correctly2019/12/22 18:55:57 Creating namespaces
exec: scripts/create-namespaces.sh
res: customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io created
namespace/openfaas created
namespace/openfaas-fn created
namespace/cert-manager created
NAME STATUS AGE
cert-manager Active 0s
default Active 7m36s
kube-node-lease Active 7m38s
kube-public Active 7m38s
kube-system Active 7m38s
openfaas Active 1s
openfaas-fn Active 0s
2019/12/22 18:56:04 0 customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io created
customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io created
namespace/openfaas created
namespace/openfaas-fn created
namespace/cert-manager created
NAME STATUS AGE
cert-manager Active 0s
default Active 7m36s
kube-node-lease Active 7m38s
kube-public Active 7m38s
kube-system Active 7m38s
openfaas Active 1s
openfaas-fn Active 0s
Building Ingress
2019/12/22 18:56:04 Creating Tiller
exec: scripts/create-tiller-sa.sh
res: serviceaccount/tiller created
clusterrolebinding.rbac.authorization.k8s.io/tiller created
2019/12/22 18:56:04 serviceaccount/tiller created
clusterrolebinding.rbac.authorization.k8s.io/tiller created
2019/12/22 18:56:04
exec: scripts/create-tiller.sh
res: $HELM_HOME has been configured at /Users/filip/.helm.
Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
2019/12/22 18:56:05 $HELM_HOME has been configured at /Users/filip/.helm.
Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
2019/12/22 18:56:05
2019/12/22 18:56:05 Is tiller ready? 1/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:07 Is tiller ready? 2/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:09 Is tiller ready? 3/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:11 Is tiller ready? 4/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:14 Is tiller ready? 5/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:16 Is tiller ready? 6/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:18 Is tiller ready? 7/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:20 Is tiller ready? 8/260
exec: ./scripts/get-tiller.sh
res:
tiller 0 <nil>
2019/12/22 18:56:22 Is tiller ready? 9/260
exec: ./scripts/get-tiller.sh
res: 1
tiller 0 1 <nil>
2019/12/22 18:56:23 Updating helm repos
exec: helm repo update
res: Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "openfaas" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
2019/12/22 18:56:24 Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "openfaas" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
2019/12/22 18:56:24
2019/12/22 18:56:24 Creating Ingress Controller
exec: scripts/install-nginx.sh
res: helm install stable/nginx-ingress --name nginxingress --set rbac.create=true
NAME: nginxingress
LAST DEPLOYED: Sun Dec 22 18:56:26 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Deployment
NAME AGE
nginxingress-nginx-ingress-controller 0s
nginxingress-nginx-ingress-default-backend 0s
==> v1/Pod(related)
NAME AGE
nginxingress-nginx-ingress-controller-5646959675-cf7jc 0s
nginxingress-nginx-ingress-default-backend-5bbf74cbf5-tkn7x 0s
==> v1/Service
NAME AGE
nginxingress-nginx-ingress-controller 0s
nginxingress-nginx-ingress-default-backend 0s
==> v1/ServiceAccount
NAME AGE
nginxingress-nginx-ingress 1s
nginxingress-nginx-ingress-backend 1s
==> v1beta1/ClusterRole
NAME AGE
nginxingress-nginx-ingress 1s
==> v1beta1/ClusterRoleBinding
NAME AGE
nginxingress-nginx-ingress 1s
==> v1beta1/Role
NAME AGE
nginxingress-nginx-ingress 1s
==> v1beta1/RoleBinding
NAME AGE
nginxingress-nginx-ingress 1s
NOTES:
The nginx-ingress controller has been installed.
It may take a few minutes for the LoadBalancer IP to be available.
You can watch the status by running 'kubectl --namespace default get services -o wide -w nginxingress-nginx-ingress-controller'
An example Ingress that makes use of the controller:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: nginx
name: example
namespace: foo
spec:
rules:
- host: www.example.com
http:
paths:
- backend:
serviceName: exampleService
servicePort: 80
path: /
# This section is only required if TLS is to be enabled for the Ingress
tls:
- hosts:
- www.example.com
secretName: example-tls
If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:
apiVersion: v1
kind: Secret
metadata:
name: example-tls
namespace: foo
data:
tls.crt: <base64 encoded cert>
tls.key: <base64 encoded key>
type: kubernetes.io/tls
2019/12/22 18:56:27 0 helm install stable/nginx-ingress --name nginxingress --set rbac.create=true
NAME: nginxingress
LAST DEPLOYED: Sun Dec 22 18:56:26 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Deployment
NAME AGE
nginxingress-nginx-ingress-controller 0s
nginxingress-nginx-ingress-default-backend 0s
==> v1/Pod(related)
NAME AGE
nginxingress-nginx-ingress-controller-5646959675-cf7jc 0s
nginxingress-nginx-ingress-default-backend-5bbf74cbf5-tkn7x 0s
==> v1/Service
NAME AGE
nginxingress-nginx-ingress-controller 0s
nginxingress-nginx-ingress-default-backend 0s
==> v1/ServiceAccount
NAME AGE
nginxingress-nginx-ingress 1s
nginxingress-nginx-ingress-backend 1s
==> v1beta1/ClusterRole
NAME AGE
nginxingress-nginx-ingress 1s
==> v1beta1/ClusterRoleBinding
NAME AGE
nginxingress-nginx-ingress 1s
==> v1beta1/Role
NAME AGE
nginxingress-nginx-ingress 1s
==> v1beta1/RoleBinding
NAME AGE
nginxingress-nginx-ingress 1s
NOTES:
The nginx-ingress controller has been installed.
It may take a few minutes for the LoadBalancer IP to be available.
You can watch the status by running 'kubectl --namespace default get services -o wide -w nginxingress-nginx-ingress-controller'
An example Ingress that makes use of the controller:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: nginx
name: example
namespace: foo
spec:
rules:
- host: www.example.com
http:
paths:
- backend:
serviceName: exampleService
servicePort: 80
path: /
# This section is only required if TLS is to be enabled for the Ingress
tls:
- hosts:
- www.example.com
secretName: example-tls
If TLS is enabled for the Ingress, a Secret containing the certificate and key must also be provided:
apiVersion: v1
kind: Secret
metadata:
name: example-tls
namespace: foo
data:
tls.crt: <base64 encoded cert>
tls.key: <base64 encoded key>
type: kubernetes.io/tls
Creating secret: s3-secret-key
exec: scripts/generate-sha.sh
res: 45ad9bd95b91a72e8b0d29ed534ae3a6a592b9ff
exec: kubectl create secret generic -n openfaas-fn s3-secret-key --from-literal=s3-secret-key=582342e7673d11229699501f876ac4e2e642425ef44613aee99e915f6d119972
res: secret/s3-secret-key created
{secret/s3-secret-key created
0}
Creating secret: s3-access-key
exec: scripts/generate-sha.sh
res: 91874f3412f5ddfb0fd4f893d689960c4c5d0396
exec: kubectl create secret generic -n openfaas-fn s3-access-key --from-literal=s3-access-key=69f92e7f89980d64d6cb78b098468fea62ba0b1714a51e8ba7cfe39ef92b526a
res: secret/s3-access-key created
{secret/s3-access-key created
0}
Creating secret: basic-auth
exec: scripts/generate-sha.sh
res: 1a343b4cf2c09e66a6e724ee848c41e11674f162
exec: kubectl create secret generic -n openfaas basic-auth --from-literal=basic-auth-user=admin --from-literal=basic-auth-password=017ca69923cdee0524607ebbfb76165b1ccc44c350023f6241fe8057ce16d5f9
res: secret/basic-auth created
{secret/basic-auth created
0}
Creating secret: payload-secret
exec: scripts/generate-sha.sh
res: 9e8aa410b9c767fdf4697d6d433a9f84c7a8c5a1
exec: kubectl create secret generic -n openfaas payload-secret --from-literal=payload-secret=3360d961fe37cabe7c9c394a85873ad7c7a9d38e58778ce9e671f99dfb055eab
res: secret/payload-secret created
{secret/payload-secret created
0}
Creating secret: jwt-private-key
exec: openssl ecparam -genkey -name prime256v1 -noout -out ./tmp/key
res:
exec: kubectl create secret generic -n openfaas jwt-private-key --from-file=key=./tmp/key
res: secret/jwt-private-key created
{secret/jwt-private-key created
0}
Creating secret: jwt-public-key
exec: openssl ec -in ./tmp/key -pubout -out ./tmp/key.pub
res:
exec: kubectl create secret generic -n openfaas jwt-public-key --from-file=key.pub=./tmp/key.pub
res: secret/jwt-public-key created
{secret/jwt-public-key created
0}
Creating secret: of-client-secret
exec: kubectl create secret generic -n openfaas of-client-secret --from-literal=of-client-secret=f946f099c8f9f9f01616987fa65105807befa4270dd17ff06066b4d8441ac95c
res: secret/of-client-secret created
{secret/of-client-secret created
0}
Creating secret: gitlab-webhook-secret
exec: scripts/generate-sha.sh
res: d50dce57a26ece29a2c4cb76fade5c01c3c8ab65
exec: kubectl create secret generic -n openfaas-fn gitlab-webhook-secret --from-literal=gitlab-webhook-secret=afcabce5663cf2a89131ebe705d354f95f4cb081a2d105bcf89f4b1d2f27c359
res: secret/gitlab-webhook-secret created
{secret/gitlab-webhook-secret created
0}
Creating secret: gitlab-api-token
exec: kubectl create secret generic -n openfaas-fn gitlab-api-token --from-literal=gitlab-api-token=kNotiNSnCTezHysynypN
res: secret/gitlab-api-token created
{secret/gitlab-api-token created
0}
Creating secret: digitalocean-dns
exec: kubectl create secret generic -n cert-manager digitalocean-dns --from-file=access-token=/Users/filip/Downloads/do-access-token
res: secret/digitalocean-dns created
{secret/digitalocean-dns created
0}
Creating secret: registry-secret
exec: kubectl create secret generic -n openfaas registry-secret --from-file=config.json=./credentials/config.json
res: secret/registry-secret created
{secret/registry-secret created
0}
Creating secret: registry-pull-secret
exec: kubectl create secret generic -n openfaas-fn registry-pull-secret --type=kubernetes.io/dockerconfigjson --from-file=.dockerconfigjson=./credentials/config.json
res: secret/registry-pull-secret created
{secret/registry-pull-secret created
0}
2019/12/22 18:56:30 Patching openfaas-fn serviceaccount for pull secrets
exec: scripts/patch-fn-serviceaccount.sh
res: serviceaccount/default patched
2019/12/22 18:56:30 serviceaccount/default patched
2019/12/22 18:56:30
2019/12/22 18:56:30 Creating Minio
exec: scripts/install-minio.sh
res: NAME: cloud-minio
LAST DEPLOYED: Sun Dec 22 18:56:32 2019
NAMESPACE: openfaas
STATUS: DEPLOYED
RESOURCES:
==> v1/ConfigMap
NAME AGE
cloud-minio 0s
==> v1/Deployment
NAME AGE
cloud-minio 0s
==> v1/Pod(related)
NAME AGE
cloud-minio-655dd45c49-lfpkt 0s
==> v1/Secret
NAME AGE
cloud-minio 0s
==> v1/Service
NAME AGE
cloud-minio 0s
==> v1/ServiceAccount
NAME AGE
cloud-minio 0s
NOTES:
Minio can be accessed via port 9000 on the following DNS name from within your cluster:
cloud-minio.openfaas.svc.cluster.local
To access Minio from localhost, run the below commands:
1. export POD_NAME=$(kubectl get pods --namespace openfaas -l "release=cloud-minio" -o jsonpath="{.items[0].metadata.name}")
2. kubectl port-forward $POD_NAME 9000 --namespace openfaas
Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/
You can now access Minio server on http://localhost:9000. Follow the below steps to connect to Minio server with mc client:
1. Download the Minio mc client - https://docs.minio.io/docs/minio-client-quickstart-guide
2. mc config host add cloud-minio-local http://localhost:9000 69f92e7f89980d64d6cb78b098468fea62ba0b1714a51e8ba7cfe39ef92b526a 582342e7673d11229699501f876ac4e2e642425ef44613aee99e915f6d119972 S3v4
3. mc ls cloud-minio-local
Alternately, you can use your browser or the Minio SDK to access the server - https://docs.minio.io/categories/17
2019/12/22 18:56:32 NAME: cloud-minio
LAST DEPLOYED: Sun Dec 22 18:56:32 2019
NAMESPACE: openfaas
STATUS: DEPLOYED
RESOURCES:
==> v1/ConfigMap
NAME AGE
cloud-minio 0s
==> v1/Deployment
NAME AGE
cloud-minio 0s
==> v1/Pod(related)
NAME AGE
cloud-minio-655dd45c49-lfpkt 0s
==> v1/Secret
NAME AGE
cloud-minio 0s
==> v1/Service
NAME AGE
cloud-minio 0s
==> v1/ServiceAccount
NAME AGE
cloud-minio 0s
NOTES:
Minio can be accessed via port 9000 on the following DNS name from within your cluster:
cloud-minio.openfaas.svc.cluster.local
To access Minio from localhost, run the below commands:
1. export POD_NAME=$(kubectl get pods --namespace openfaas -l "release=cloud-minio" -o jsonpath="{.items[0].metadata.name}")
2. kubectl port-forward $POD_NAME 9000 --namespace openfaas
Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/
You can now access Minio server on http://localhost:9000. Follow the below steps to connect to Minio server with mc client:
1. Download the Minio mc client - https://docs.minio.io/docs/minio-client-quickstart-guide
2. mc config host add cloud-minio-local http://localhost:9000 69f92e7f89980d64d6cb78b098468fea62ba0b1714a51e8ba7cfe39ef92b526a 582342e7673d11229699501f876ac4e2e642425ef44613aee99e915f6d119972 S3v4
3. mc ls cloud-minio-local
Alternately, you can use your browser or the Minio SDK to access the server - https://docs.minio.io/categories/17
2019/12/22 18:56:32
2019/12/22 18:56:32 Creating Cert-Manager
exec: scripts/install-cert-manager.sh
res: "jetstack" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "openfaas" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
NAME: cert-manager
LAST DEPLOYED: Sun Dec 22 18:56:35 2019
NAMESPACE: cert-manager
STATUS: DEPLOYED
RESOURCES:
==> v1/ClusterRole
NAME AGE
cert-manager-edit 2s
cert-manager-view 2s
cert-manager-webhook:webhook-requester 2s
==> v1/Deployment
NAME AGE
cert-manager 2s
cert-manager-cainjector 2s
cert-manager-webhook 2s
==> v1/Pod(related)
NAME AGE
cert-manager-55c44f98f-zz72c 2s
cert-manager-cainjector-576978ffc8-jzhcn 2s
cert-manager-webhook-c67fbc858-j7gmz 2s
==> v1/Service
NAME AGE
cert-manager 2s
cert-manager-webhook 2s
==> v1/ServiceAccount
NAME AGE
cert-manager 2s
cert-manager-cainjector 2s
cert-manager-webhook 2s
==> v1beta1/APIService
NAME AGE
v1beta1.webhook.cert-manager.io 2s
==> v1beta1/ClusterRole
NAME AGE
cert-manager-cainjector 2s
cert-manager-controller-certificates 2s
cert-manager-controller-challenges 2s
cert-manager-controller-clusterissuers 2s
cert-manager-controller-ingress-shim 2s
cert-manager-controller-issuers 2s
cert-manager-controller-orders 2s
==> v1beta1/ClusterRoleBinding
NAME AGE
cert-manager-cainjector 2s
cert-manager-controller-certificates 2s
cert-manager-controller-challenges 2s
cert-manager-controller-clusterissuers 2s
cert-manager-controller-ingress-shim 2s
cert-manager-controller-issuers 2s
cert-manager-controller-orders 2s
cert-manager-leaderelection 2s
cert-manager-webhook:auth-delegator 2s
==> v1beta1/MutatingWebhookConfiguration
NAME AGE
cert-manager-webhook 2s
==> v1beta1/Role
NAME AGE
cert-manager-cainjector:leaderelection 2s
cert-manager:leaderelection 2s
==> v1beta1/RoleBinding
NAME AGE
cert-manager-cainjector:leaderelection 2s
cert-manager-webhook:webhook-authentication-reader 2s
cert-manager:leaderelection 2s
==> v1beta1/ValidatingWebhookConfiguration
NAME AGE
cert-manager-webhook 2s
NOTES:
cert-manager has been deployed successfully!
In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).
More information on the different types of issuers and how to configure them
can be found in our documentation:
https://docs.cert-manager.io/en/latest/reference/issuers.html
For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:
https://docs.cert-manager.io/en/latest/reference/ingress-shim.html
2019/12/22 18:56:38 0 "jetstack" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "openfaas" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
NAME: cert-manager
LAST DEPLOYED: Sun Dec 22 18:56:35 2019
NAMESPACE: cert-manager
STATUS: DEPLOYED
RESOURCES:
==> v1/ClusterRole
NAME AGE
cert-manager-edit 2s
cert-manager-view 2s
cert-manager-webhook:webhook-requester 2s
==> v1/Deployment
NAME AGE
cert-manager 2s
cert-manager-cainjector 2s
cert-manager-webhook 2s
==> v1/Pod(related)
NAME AGE
cert-manager-55c44f98f-zz72c 2s
cert-manager-cainjector-576978ffc8-jzhcn 2s
cert-manager-webhook-c67fbc858-j7gmz 2s
==> v1/Service
NAME AGE
cert-manager 2s
cert-manager-webhook 2s
==> v1/ServiceAccount
NAME AGE
cert-manager 2s
cert-manager-cainjector 2s
cert-manager-webhook 2s
==> v1beta1/APIService
NAME AGE
v1beta1.webhook.cert-manager.io 2s
==> v1beta1/ClusterRole
NAME AGE
cert-manager-cainjector 2s
cert-manager-controller-certificates 2s
cert-manager-controller-challenges 2s
cert-manager-controller-clusterissuers 2s
cert-manager-controller-ingress-shim 2s
cert-manager-controller-issuers 2s
cert-manager-controller-orders 2s
==> v1beta1/ClusterRoleBinding
NAME AGE
cert-manager-cainjector 2s
cert-manager-controller-certificates 2s
cert-manager-controller-challenges 2s
cert-manager-controller-clusterissuers 2s
cert-manager-controller-ingress-shim 2s
cert-manager-controller-issuers 2s
cert-manager-controller-orders 2s
cert-manager-leaderelection 2s
cert-manager-webhook:auth-delegator 2s
==> v1beta1/MutatingWebhookConfiguration
NAME AGE
cert-manager-webhook 2s
==> v1beta1/Role
NAME AGE
cert-manager-cainjector:leaderelection 2s
cert-manager:leaderelection 2s
==> v1beta1/RoleBinding
NAME AGE
cert-manager-cainjector:leaderelection 2s
cert-manager-webhook:webhook-authentication-reader 2s
cert-manager:leaderelection 2s
==> v1beta1/ValidatingWebhookConfiguration
NAME AGE
cert-manager-webhook 2s
NOTES:
cert-manager has been deployed successfully!
In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).
More information on the different types of issuers and how to configure them
can be found in our documentation:
https://docs.cert-manager.io/en/latest/reference/issuers.html
For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:
https://docs.cert-manager.io/en/latest/reference/ingress-shim.html
2019/12/22 18:56:38 Creating secrets for functions to consume
exec: scripts/create-functions-auth.sh
res: secret/basic-auth-user created
secret/basic-auth-password created
2019/12/22 18:56:38 secret/basic-auth-user created
secret/basic-auth-password created
2019/12/22 18:56:38
2019/12/22 18:56:38 Creating OpenFaaS
exec: scripts/install-openfaas.sh
res: "openfaas" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "openfaas" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Release "openfaas" does not exist. Installing it now.
2019/12/22 18:56:41 0 "openfaas" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "openfaas" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Release "openfaas" does not exist. Installing it now.
Error: Could not get apiVersions from Kubernetes: unable to retrieve the complete list of server APIs: webhook.cert-manager.io/v1beta1: the server is currently unable to handle the request
2019/12/22 18:56:41 Is cert-manager ready? 1/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:56:44 Is cert-manager ready? 2/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:56:46 Is cert-manager ready? 3/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:56:49 Is cert-manager ready? 4/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:56:51 Is cert-manager ready? 5/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:56:54 Is cert-manager ready? 6/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:56:57 Is cert-manager ready? 7/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:56:59 Is cert-manager ready? 8/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:02 Is cert-manager ready? 9/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:04 Is cert-manager ready? 10/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:07 Is cert-manager ready? 11/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:09 Is cert-manager ready? 12/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:12 Is cert-manager ready? 13/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:14 Is cert-manager ready? 14/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:17 Is cert-manager ready? 15/260
exec: ./scripts/get-cert-manager.sh
res:
cert-manager 0 <nil>
2019/12/22 18:57:19 Is cert-manager ready? 16/260
exec: ./scripts/get-cert-manager.sh
res: True
cert-manager 0 True <nil>
exec: kubectl apply -f tmp/generated-ingress-ingress-wildcard.yaml
res: ingress.extensions/openfaas-ingress created
2019/12/22 18:57:20 0 ingress.extensions/openfaas-ingress created
exec: kubectl apply -f tmp/generated-ingress-ingress-auth.yaml
res: ingress.extensions/openfaas-auth-ingress created
2019/12/22 18:57:21 0 ingress.extensions/openfaas-auth-ingress created
exec: kubectl apply -f tmp/generated-tls-issuer-prod.yml
res: clusterissuer.cert-manager.io/letsencrypt-prod created
2019/12/22 18:57:22 0 clusterissuer.cert-manager.io/letsencrypt-prod created
exec: kubectl apply -f tmp/generated-tls-issuer-staging.yml
res: clusterissuer.cert-manager.io/letsencrypt-staging created
2019/12/22 18:57:22 0 clusterissuer.cert-manager.io/letsencrypt-staging created
exec: kubectl apply -f tmp/generated-tls-wildcard-domain-cert.yml
res: certificate.cert-manager.io/wildcard-cluster.devflow.site created
2019/12/22 18:57:23 0 certificate.cert-manager.io/wildcard-cluster.devflow.site created
exec: kubectl apply -f tmp/generated-tls-auth-domain-cert.yml
res: certificate.cert-manager.io/auth-system-cluster.devflow.site created
2019/12/22 18:57:23 0 certificate.cert-manager.io/auth-system-cluster.devflow.site created
Creating stack.yml
2019/12/22 18:57:23 Creating SealedSecrets
exec: scripts/install-sealedsecrets.sh
res: SealedSecrets release: v0.9.6
NAME: ofc-sealedsecrets
LAST DEPLOYED: Sun Dec 22 18:57:25 2019
NAMESPACE: kube-system
STATUS: DEPLOYED
RESOURCES:
==> v1/ClusterRole
NAME AGE
secrets-unsealer 0s
==> v1/ClusterRoleBinding
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1/Deployment
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1/Pod(related)
NAME AGE
ofc-sealedsecrets-sealed-secrets-7bc4875b88-rvz2k 0s
==> v1/Role
NAME AGE
ofc-sealedsecrets-sealed-secrets-key-admin 0s
ofc-sealedsecrets-sealed-secrets-service-proxier 0s
==> v1/RoleBinding
NAME AGE
ofc-sealedsecrets-sealed-secrets-key-admin 0s
ofc-sealedsecrets-sealed-secrets-service-proxier 0s
==> v1/Service
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1/ServiceAccount
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1beta1/CustomResourceDefinition
NAME AGE
sealedsecrets.bitnami.com 0s
NOTES:
You should now be able to create sealed secrets.
1. Install client-side tool into /usr/local/bin/
GOOS=$(go env GOOS)
GOARCH=$(go env GOARCH)
wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.9.6/kubeseal-$GOOS-$GOARCH
sudo install -m 755 kubeseal-$GOOS-$GOARCH /usr/local/bin/kubeseal
2. Create a sealed secret file
# note the use of `--dry-run` - this does not create a secret in your cluster
kubectl create secret generic secret-name --dry-run --from-literal=foo=bar -o [json|yaml] | \
kubeseal \
--controller-name=ofc-sealedsecrets-sealed-secrets \
--controller-namespace=kube-system \
--format [json|yaml] > mysealedsecret.[json|yaml]
The file mysealedsecret.[json|yaml] is a commitable file.
If you would rather not need access to the cluster to generate the sealed secret you can run
kubeseal \
--controller-name=ofc-sealedsecrets-sealed-secrets \
--controller-namespace=kube-system \
--fetch-cert > mycert.pem
to retrieve the public cert used for encryption and store it locally. You can then run 'kubeseal --cert mycert.pem' instead to use the local cert e.g.
kubectl create secret generic secret-name --dry-run --from-literal=foo=bar -o [json|yaml] | \
kubeseal \
--controller-name=ofc-sealedsecrets-sealed-secrets \
--controller-namespace=kube-system \
--format [json|yaml] --cert mycert.pem > mysealedsecret.[json|yaml]
3. Apply the sealed secret
kubectl create -f mysealedsecret.[json|yaml]
Running 'kubectl get secret secret-name -o [json|yaml]' will show the decrypted secret that was generated from the sealed secret.
Both the SealedSecret and generated Secret must have the same name and namespace.
2019/12/22 18:57:26 SealedSecrets release: v0.9.6
NAME: ofc-sealedsecrets
LAST DEPLOYED: Sun Dec 22 18:57:25 2019
NAMESPACE: kube-system
STATUS: DEPLOYED
RESOURCES:
==> v1/ClusterRole
NAME AGE
secrets-unsealer 0s
==> v1/ClusterRoleBinding
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1/Deployment
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1/Pod(related)
NAME AGE
ofc-sealedsecrets-sealed-secrets-7bc4875b88-rvz2k 0s
==> v1/Role
NAME AGE
ofc-sealedsecrets-sealed-secrets-key-admin 0s
ofc-sealedsecrets-sealed-secrets-service-proxier 0s
==> v1/RoleBinding
NAME AGE
ofc-sealedsecrets-sealed-secrets-key-admin 0s
ofc-sealedsecrets-sealed-secrets-service-proxier 0s
==> v1/Service
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1/ServiceAccount
NAME AGE
ofc-sealedsecrets-sealed-secrets 0s
==> v1beta1/CustomResourceDefinition
NAME AGE
sealedsecrets.bitnami.com 0s
NOTES:
You should now be able to create sealed secrets.
1. Install client-side tool into /usr/local/bin/
GOOS=$(go env GOOS)
GOARCH=$(go env GOARCH)
wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.9.6/kubeseal-$GOOS-$GOARCH
sudo install -m 755 kubeseal-$GOOS-$GOARCH /usr/local/bin/kubeseal
2. Create a sealed secret file
# note the use of `--dry-run` - this does not create a secret in your cluster
kubectl create secret generic secret-name --dry-run --from-literal=foo=bar -o [json|yaml] | \
kubeseal \
--controller-name=ofc-sealedsecrets-sealed-secrets \
--controller-namespace=kube-system \
--format [json|yaml] > mysealedsecret.[json|yaml]
The file mysealedsecret.[json|yaml] is a commitable file.
If you would rather not need access to the cluster to generate the sealed secret you can run
kubeseal \
--controller-name=ofc-sealedsecrets-sealed-secrets \
--controller-namespace=kube-system \
--fetch-cert > mycert.pem
to retrieve the public cert used for encryption and store it locally. You can then run 'kubeseal --cert mycert.pem' instead to use the local cert e.g.
kubectl create secret generic secret-name --dry-run --from-literal=foo=bar -o [json|yaml] | \
kubeseal \
--controller-name=ofc-sealedsecrets-sealed-secrets \
--controller-namespace=kube-system \
--format [json|yaml] --cert mycert.pem > mysealedsecret.[json|yaml]
3. Apply the sealed secret
kubectl create -f mysealedsecret.[json|yaml]
Running 'kubectl get secret secret-name -o [json|yaml]' will show the decrypted secret that was generated from the sealed secret.
Both the SealedSecret and generated Secret must have the same name and namespace.
2019/12/22 18:57:26
2019/12/22 18:57:26 Are SealedSecrets ready? 1/260
exec: ./scripts/get-sealedsecretscontroller.sh
res:
sealedsecretscontroller 0 <nil>
2019/12/22 18:57:28 Are SealedSecrets ready? 2/260
exec: ./scripts/get-sealedsecretscontroller.sh
res:
sealedsecretscontroller 0 <nil>
2019/12/22 18:57:30 Are SealedSecrets ready? 3/260
exec: ./scripts/get-sealedsecretscontroller.sh
res:
sealedsecretscontroller 0 <nil>
2019/12/22 18:57:33 Are SealedSecrets ready? 4/260
exec: ./scripts/get-sealedsecretscontroller.sh
res:
sealedsecretscontroller 0 <nil>
2019/12/22 18:57:35 Are SealedSecrets ready? 5/260
exec: ./scripts/get-sealedsecretscontroller.sh
res:
sealedsecretscontroller 0 <nil>
2019/12/22 18:57:37 Are SealedSecrets ready? 6/260
exec: ./scripts/get-sealedsecretscontroller.sh
res:
sealedsecretscontroller 0 <nil>
2019/12/22 18:57:39 Are SealedSecrets ready? 7/260
exec: ./scripts/get-sealedsecretscontroller.sh
res:
sealedsecretscontroller 0 <nil>
2019/12/22 18:57:41 Are SealedSecrets ready? 8/260
exec: ./scripts/get-sealedsecretscontroller.sh
res: 1
sealedsecretscontroller 0 1 <nil>
exec: ./scripts/export-sealed-secret-pubcert.sh
res: -----BEGIN CERTIFICATE-----
MIIErjCCApagAwIBAgIRAKVLLZuodcA6FaZ98rnemlowDQYJKoZIhvcNAQELBQAw
ADAeFw0xOTEyMjIxNzU3NDFaFw0yOTEyMTkxNzU3NDFaMAAwggIiMA0GCSqGSIb3
DQEBAQUAA4ICDwAwggIKAoICAQDjlnLLUH/oSyD197Xaq1YrTarrGbBopoZVH3K4
sGqwNj5IA9um+GTZSRzFL4hkI78csXm3dVSZ71JyGBN9CUvAD746ocoG7mev/Oei
lVOcBlO1hud2/FvC8ckzxILwJN2kU3cFvPaOH/dRs1CkQ0enVbfhZbuTTriLrnyt
FXjaQFqRm2qG2qvkc9BXdJ/ZTjYmyjPOLs/9udBZTZwr7kw/07sljQNzjW/bD5co
kx0h/pXnEfflIFx5viahQ9WIuXuD60lMVmPY6jW3jfk7/vCHiLY0z555di+I04i8
nZA6QodkomZRpCR8Dca5hBUlMLdC/6GHuOrnd8j566CByiTDcrDRrTJV8WTuD9N0
eGkAv2KtWLvzuw7aPWeMc4pO/P9iRt9mIf59O+xqbnT1sDxiLzTwomNVABprPRfN
FIeXYjnjpFtx+Pa1xk7oQIgJ1Sib60ZgH6trMEetH7Z9Vrfl0D1HRaogoZtkVrQo
9J3WLwo2QDaJLuTirDO3Afu7PyR9m6SqexF3tKWiJTNS+KWyPw+P83+2rBB7xgdR
ZZYX982NrIeh2v2Adybl2qDx7s+bpeTbantLLA37Ug4Yah0MCUL49sR6MJpL/U8Y
IylLZRwwrrHyd+8GzkTinj1mLUJnXccPofKbNxKReb3WwwTApaEZsb+jWuj89aJS
O0+eUwIDAQABoyMwITAOBgNVHQ8BAf8EBAMCAAEwDwYDVR0TAQH/BAUwAwEB/zAN
BgkqhkiG9w0BAQsFAAOCAgEApr/2NkOf1dcjJxh0mm7gNkJE/upc/euU+XFt42Vu
nxDjfzz4br4eC30/yFTUBqRl/XD44ZQr7ZE+1F96HITDd3Z4/WwxVw+XlwrbEXvP
KS40K+otMblKPimhdV8UInPNL1SChUsnNbbljg6Sk3E0Y5EVjmJ4+lcYurR1ElVR
O1BGRdM/jVlIKXcDz2m7N8ywBpStUD0tWxe5ahctfkq9/UXL9LBJ4DKG6UgBReSE
Uf55Omaz5CbVFBuSS9/h5iP/9ikdI38EXFlheP/n23iFzE330qnrW4PA04hxTMQ8
NNMFm6TP//y4cSrYzaFhEThXaLOBFwWzTmU5O92m6r756EXKQb0Yx17oFhyIUMjJ
WgDbAAV9pZ7omnHl5nTDKO9CToxM8kobwdXZf2BI1l7gGzMhew7D2SK9/sYBZGNh
r6UvIfLOMfOSUZQ2Xw71o4j7KGqTpsj0b05WFYXV7VsMhOCiQlHA5Svu8ybEbFve
uWWxd/R/ZrySLkJPUnaWgy2sGVdT4XIlQNMTGAhCnRmcJs+BG9Q2nQGInk0BxKIM
mmgkCmPYvPmDrDeV/4zN7NgJGkSEQAmndIUiQ+ydhedBGdtZHwvXzp+1NSMA4Q5f
07Ee4ttsmVh6KMkq1zaZ4uEfdGP7nzWkADb5fDk6GSAoBO4RfMW4XJrv9PlEnlXe
L/w=
-----END CERTIFICATE-----
secrets cert 0 -----BEGIN CERTIFICATE-----
MIIErjCCApagAwIBAgIRAKVLLZuodcA6FaZ98rnemlowDQYJKoZIhvcNAQELBQAw
ADAeFw0xOTEyMjIxNzU3NDFaFw0yOTEyMTkxNzU3NDFaMAAwggIiMA0GCSqGSIb3
DQEBAQUAA4ICDwAwggIKAoICAQDjlnLLUH/oSyD197Xaq1YrTarrGbBopoZVH3K4
sGqwNj5IA9um+GTZSRzFL4hkI78csXm3dVSZ71JyGBN9CUvAD746ocoG7mev/Oei
lVOcBlO1hud2/FvC8ckzxILwJN2kU3cFvPaOH/dRs1CkQ0enVbfhZbuTTriLrnyt
FXjaQFqRm2qG2qvkc9BXdJ/ZTjYmyjPOLs/9udBZTZwr7kw/07sljQNzjW/bD5co
kx0h/pXnEfflIFx5viahQ9WIuXuD60lMVmPY6jW3jfk7/vCHiLY0z555di+I04i8
nZA6QodkomZRpCR8Dca5hBUlMLdC/6GHuOrnd8j566CByiTDcrDRrTJV8WTuD9N0
eGkAv2KtWLvzuw7aPWeMc4pO/P9iRt9mIf59O+xqbnT1sDxiLzTwomNVABprPRfN
FIeXYjnjpFtx+Pa1xk7oQIgJ1Sib60ZgH6trMEetH7Z9Vrfl0D1HRaogoZtkVrQo
9J3WLwo2QDaJLuTirDO3Afu7PyR9m6SqexF3tKWiJTNS+KWyPw+P83+2rBB7xgdR
ZZYX982NrIeh2v2Adybl2qDx7s+bpeTbantLLA37Ug4Yah0MCUL49sR6MJpL/U8Y
IylLZRwwrrHyd+8GzkTinj1mLUJnXccPofKbNxKReb3WwwTApaEZsb+jWuj89aJS
O0+eUwIDAQABoyMwITAOBgNVHQ8BAf8EBAMCAAEwDwYDVR0TAQH/BAUwAwEB/zAN
BgkqhkiG9w0BAQsFAAOCAgEApr/2NkOf1dcjJxh0mm7gNkJE/upc/euU+XFt42Vu
nxDjfzz4br4eC30/yFTUBqRl/XD44ZQr7ZE+1F96HITDd3Z4/WwxVw+XlwrbEXvP
KS40K+otMblKPimhdV8UInPNL1SChUsnNbbljg6Sk3E0Y5EVjmJ4+lcYurR1ElVR
O1BGRdM/jVlIKXcDz2m7N8ywBpStUD0tWxe5ahctfkq9/UXL9LBJ4DKG6UgBReSE
Uf55Omaz5CbVFBuSS9/h5iP/9ikdI38EXFlheP/n23iFzE330qnrW4PA04hxTMQ8
NNMFm6TP//y4cSrYzaFhEThXaLOBFwWzTmU5O92m6r756EXKQb0Yx17oFhyIUMjJ
WgDbAAV9pZ7omnHl5nTDKO9CToxM8kobwdXZf2BI1l7gGzMhew7D2SK9/sYBZGNh
r6UvIfLOMfOSUZQ2Xw71o4j7KGqTpsj0b05WFYXV7VsMhOCiQlHA5Svu8ybEbFve
uWWxd/R/ZrySLkJPUnaWgy2sGVdT4XIlQNMTGAhCnRmcJs+BG9Q2nQGInk0BxKIM
mmgkCmPYvPmDrDeV/4zN7NgJGkSEQAmndIUiQ+ydhedBGdtZHwvXzp+1NSMA4Q5f
07Ee4ttsmVh6KMkq1zaZ4uEfdGP7nzWkADb5fDk6GSAoBO4RfMW4XJrv9PlEnlXe
L/w=
-----END CERTIFICATE-----
<nil>
exec: ./scripts/clone-cloud-components.sh
res: Checking out openfaas/openfaas-cloud@0.12.0
{Checking out openfaas/openfaas-cloud@0.12.0
Cloning into './tmp/openfaas-cloud'...
Checking out files: 97% (3671/3763)
Checking out files: 98% (3688/3763)
Checking out files: 99% (3726/3763)
Checking out files: 100% (3763/3763)
Checking out files: 100% (3763/3763), done.
Note: checking out '0.12.0'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
HEAD is now at af642cb Rename system-metrics to metrics #551
0}
exec: ./scripts/deploy-cloud-components.sh
res: service/of-builder created
deployment.apps/of-builder created
clusterrole.rbac.authorization.k8s.io/sealedsecrets-importer created
rolebinding.rbac.authorization.k8s.io/manage-sealed-secrets created
serviceaccount/sealedsecrets-importer-rw created
deployment.apps/edge-auth created
service/edge-auth created
deployment.apps/edge-router created
service/edge-router created
service/edge-auth unchanged
Creating payload-secret in openfaas-fn
secret/payload-secret created
Fetch templates from repository: https://github.com/openfaas/templates.git at master
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Calling the OpenFaaS server to validate the credentials...
Cannot connect to OpenFaaS on URL: http://127.0.0.1:31111. Get http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: garbage-collect.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: pipeline-log.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: audit-event.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: echo.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: system-metrics.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: buildshiprun.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: import-secrets.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: list-functions.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: function-logs.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: git-tar.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Function 'system-metrics' failed to deploy with status code: 500
Function 'buildshiprun' failed to deploy with status code: 500
Function 'import-secrets' failed to deploy with status code: 500
Function 'list-functions' failed to deploy with status code: 500
Function 'function-logs' failed to deploy with status code: 500
Function 'garbage-collect' failed to deploy with status code: 500
Function 'pipeline-log' failed to deploy with status code: 500
Function 'echo' failed to deploy with status code: 500
Function 'audit-event' failed to deploy with status code: 500
Function 'git-tar' failed to deploy with status code: 500
Deploying gitlab functions...
Deploying: git-tar.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: system-gitlab-event.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: gitlab-status.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: gitlab-push.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Function 'git-tar' failed to deploy with status code: 500
Function 'system-gitlab-event' failed to deploy with status code: 500
Function 'gitlab-status' failed to deploy with status code: 500
Function 'gitlab-push' failed to deploy with status code: 500
Fetch templates from repository: https://github.com/openfaas-incubator/node10-express-template at master
Deploying: system-dashboard.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Function 'system-dashboard' failed to deploy with status code: 500
{service/of-builder created
deployment.apps/of-builder created
clusterrole.rbac.authorization.k8s.io/sealedsecrets-importer created
rolebinding.rbac.authorization.k8s.io/manage-sealed-secrets created
serviceaccount/sealedsecrets-importer-rw created
deployment.apps/edge-auth created
service/edge-auth created
deployment.apps/edge-router created
service/edge-router created
service/edge-auth unchanged
Creating payload-secret in openfaas-fn
secret/payload-secret created
Fetch templates from repository: https://github.com/openfaas/templates.git at master
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Checking if OpenFaaS GW is up.
Calling the OpenFaaS server to validate the credentials...
Cannot connect to OpenFaaS on URL: http://127.0.0.1:31111. Get http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: garbage-collect.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: pipeline-log.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: audit-event.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: echo.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: system-metrics.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: buildshiprun.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: import-secrets.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: list-functions.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: function-logs.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: git-tar.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Function 'system-metrics' failed to deploy with status code: 500
Function 'buildshiprun' failed to deploy with status code: 500
Function 'import-secrets' failed to deploy with status code: 500
Function 'list-functions' failed to deploy with status code: 500
Function 'function-logs' failed to deploy with status code: 500
Function 'garbage-collect' failed to deploy with status code: 500
Function 'pipeline-log' failed to deploy with status code: 500
Function 'echo' failed to deploy with status code: 500
Function 'audit-event' failed to deploy with status code: 500
Function 'git-tar' failed to deploy with status code: 500
Deploying gitlab functions...
Deploying: git-tar.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: system-gitlab-event.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: gitlab-status.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Deploying: gitlab-push.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Function 'git-tar' failed to deploy with status code: 500
Function 'system-gitlab-event' failed to deploy with status code: 500
Function 'gitlab-status' failed to deploy with status code: 500
Function 'gitlab-push' failed to deploy with status code: 500
Fetch templates from repository: https://github.com/openfaas-incubator/node10-express-template at master
Deploying: system-dashboard.
WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.
Is OpenFaaS deployed? Do you need to specify the --gateway flag?
Put http://127.0.0.1:31111/system/functions: dial tcp 127.0.0.1:31111: connect: connection refused
Function 'system-dashboard' failed to deploy with status code: 500
2019/12/22 18:57:51 Attempting to expand templates from https://github.com/openfaas/templates.git
2019/12/22 18:57:52 Fetched 17 template(s) : [csharp csharp-armhf dockerfile go go-armhf java12 java8 node node-arm64 node-armhf node12 php7 python python-armhf python3 python3-armhf ruby] from https://github.com/openfaas/templates.git
Error from server (NotFound): services "gateway" not found
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 31111: Connection refused
2019/12/22 18:58:56 Attempting to expand templates from https://github.com/openfaas-incubator/node10-express-template
2019/12/22 18:58:57 Fetched 3 template(s) : [node10-express node10-express-arm64 node10-express-armhf] from https://github.com/openfaas-incubator/node10-express-template
0}
Plan completed in 181.924568 seconds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment