Dit artikel einiget de searje oersette notysjes oer OpenWhisk fan 'e skriuwer . Hjoed sille wy sjen nei it proses fan it ynsetten fan OpenWhisk oer Kubernetes mei korrizjearre kommando's om te wurkjen mei aktuele ferzjes fan applikaasjes. It sil ek it proses dekke fan it útfieren fan OpenWhisk-funksjes mei Knative en TektonCD op Kubernetes mei de Nodejs runtime.
OpenWhisk ynsette op Kubernetes
Yn 'e rin fan in pear dagen eksperimintearre ik mei it ynsetten fan OpenWhisk nei Kubernetes om in ienfâldige en rappe testgrûn te meitsjen. En om't ik nij bin by Kubernetes, leau ik dat in dei en in heale dei waard bestege oan suksesfolle ynset. YN De repositories hawwe heul dúdlike ynstruksjes foar it ynsetten fan OpenWhisk op Kubernetes. Hjir binne de ynset ynstruksjes makke foar Mac (Ik sil ek alles dwaan op Linux omdat ik leaver Linux. — ca. oersetter).
- It ynstallearjen fan de pakketbehearder
asdf, wêrnei't wy automatysk korrigearje~/.bash_profileof syn ekwivalint lykas dit:
$ brew install asdf
$ [ -s "/usr/local/opt/asdf/asdf.sh" ] && . /usr/local/opt/asdf/asdf.sh
$ source ~/.bash_profile- Plugins tafoegje
minikubeиkubelet:
$ asdf plugin-add kubectl
$ asdf plugin-add minikube- Ynstallearje minikube en kubelet:
$ asdf install kubectl 1.9.0
$ asdf global kubectl 1.9.0
$ asdf install minikube 0.25.2
$ asdf global minikube 0.25.2Op Linux wurdt dizze stap sa dien (alles wurdt yn ~/bin pleatst, dat stiet yn myn PATH, oersetternotysje):
$ curl -L0 minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && chmod +x minikube && mv minikube ~/bin/
$ curl -L0 https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x kubectl && mv kubectl ~/bin/- Meitsje in firtuele minikube-masine (VirtualBox moat foarôf ynstalleare wurde):
$ minikube start --cpus 2 --memory 4096 --kubernetes-version=v1.9.0 --extra-config=apiserver.Authorization.Mode=RBACminikube start , sûnder parameters en mei standertwearden. — ca. oersetter]
$ minikube start
minikube v1.5.2 on Debian 8.11
Automatically selected the 'virtualbox' driver
Downloading VM boot image ...
> minikube-v1.5.1.iso.sha256: 65 B / 65 B [--------------] 100.00% ? p/s 0s
> minikube-v1.5.1.iso: 143.76 MiB / 143.76 MiB [-] 100.00% 5.63 MiB p/s 26s
Creating virtualbox VM (CPUs=2, Memory=4096MB, Disk=20000MB) ...
Preparing Kubernetes v1.16.2 on Docker '18.09.9' ...
Downloading kubelet v1.16.2
Downloading kubeadm v1.16.2
Pulling images ...
Launching Kubernetes ... Waiting for: apiserver
Done! kubectl is now configured to use "minikube"- It netwurk yn Docker wikselje nei promiskueuze modus:
$ minikube ssh -- sudo ip link set docker0 promisc on- Meitsje in nammeromte en markearje it wurkknooppunt:
$ kubectl create namespace openwhisk
$ kubectl label nodes --all openwhisk-role=invoker- Wy krije de ynhâld fan it repository en oerskriuwe it type foar yngong yn it mycluster.yaml-bestân:
$ git clone https://github.com/apache/incubator-openwhisk-deploy-kube.git
$ cd incubator-openwhisk-deploy-kube/
$ cat << "EOF" > mycluster.yaml
whisk:
ingress:
type: NodePort
api_host_name: 192.168.99.100
api_host_port: 31001
nginx:
httpsNodePort: 31001
EOF- Ynstallearje Helm en ynsette it mei it:
$ brew install kubernetes-helm
$ helm init # init Helm Tiller, не нужно на Helm v3+
$ kubectl get pods -n kube-system # verify that tiller-deploy is in the running state, не нужно на helm v3+
$ kubectl create clusterrolebinding tiller-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default
$ helm install ./openwhisk/helm/ --namespace=openwhisk -f mycluster.yaml$ curl -L0 https://get.helm.sh/helm-v3.0.1-linux-amd64.tar.gz | tar -xzvf - linux-amd64/helm --strip-components=1; sudo mv helm /usr/local/bin
$ kubectl create clusterrolebinding tiller-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default
$ helm install ./openwhisk/helm/ --namespace=openwhisk --generate-name -f mycluster.yaml- Wy kontrolearje dat alles opstien is (STATUS = Running of Completed):
$ kubectl get pods -n openwhisk
NAME READY STATUS RESTARTS AGE
openwhisk-1576070780-alarmprovider-6868dc694-plvpf 1/1 Running 1 1d5h
openwhisk-1576070780-apigateway-8d56f4979-825hf 1/1 Running 1 1d5h
openwhisk-1576070780-cloudantprovider-544bb46596-9scph 1/1 Running 1 1d5h
openwhisk-1576070780-controller-0 1/1 Running 2 1d5h
openwhisk-1576070780-couchdb-7fd7f6c7cc-42tw6 1/1 Running 1 1d5h
openwhisk-1576070780-gen-certs-z9nsb 0/1 Completed 0 1d5h
openwhisk-1576070780-init-couchdb-r2vmt 0/1 Completed 0 1d5h
openwhisk-1576070780-install-packages-27dtr 0/1 Completed 0 1d4h
openwhisk-1576070780-invoker-0 1/1 Running 1 1d5h
openwhisk-1576070780-kafka-0 1/1 Running 1 1d5h
openwhisk-1576070780-kafkaprovider-f8b4cf4fc-7z4gt 1/1 Running 1 1d5h
openwhisk-1576070780-nginx-6dbdbf69bc-5x76n 1/1 Running 1 1d5h
openwhisk-1576070780-redis-cfd8756f4-hkrt6 1/1 Running 1 1d5h
openwhisk-1576070780-wskadmin 1/1 Running 1 1d5h
openwhisk-1576070780-zookeeper-0 1/1 Running 1 1d5h
wskopenwhisk-1576070780-invoker-00-1-prewarm-nodejs10 1/1 Running 0 61s
wskopenwhisk-1576070780-invoker-00-2-prewarm-nodejs10 1/1 Running 0 61s
wskopenwhisk-1576070780-invoker-00-3-whisksystem-invokerhealtht 1/1 Running 0 59s- Wsk konfigurearje om te wurkjen:
$ wsk property set --apihost 192.168.99.100:31001
$ wsk property set --auth 23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwPWy kontrolearje:
$ wsk -i list
Entities in namespace: default
packages
actions
triggers
rulesProblemen en harren oplossings
getsockopt: ferbining wegere
$ wsk -i list
error: Unable to obtain the list of entities for namespace 'default': Get http://192.168.99.100:31001/api/v1/namespaces/_/actions?limit=0&skip=0: dial tcp 192.168.99.100:31001: getsockopt: connection refusedKontrolearje dat de konteners yn 'e nammeromte binne openwhisk yn status Running, omdat soms crashes it mei flaters CreateContainerConfigError.
Invoker is noch inisjalisearjend - Init: 1/2
It proses fan it downloaden fan ferskate runtime-omjouwings kin in lange tiid duorje. Om dingen te rapperjen, kinne jo in ferkoarte minimumlist yn it bestân opjaan mycluster.yaml:
whisk:
runtimes: "runtimes-minimal-travis.json"Container mei namme -ynstallearje-pakketten- crashes nei Flater
Ferheegje gewoan de timeouts foar livenesstests.
Ynstallaasje fan OpenWhisk oer Knative
Priti Desai útfierde de ynstallaasje boppe op in kluster yn 'e IBM-wolk, lykas op in gewoane minikube, mei Knative Build en BuildTemplates. Ik sil ek ynstallearje boppe op minukube, basearre op hoe yn ús blog earder - mei de lêste softwareferzjes. Sûnt Knative Build en BuildTemplates binne offisjeel ôfskreaun, Ik sil brûke de oanrikkemandearre ferfanging yn 'e foarm fan Tekton Pipelines. De rest fan it artikel is skreaun nei it lêzen fan de dokumintaasje foar Tekton Pipelines, mar is basearre op de ideeën fan Priti. Om te wurkjen sille jo tagong hawwe ta wat Docker Registry - ik, lykas de orizjinele auteur, sil DockerHub brûke.
$ curl -L0 https://github.com/solo-io/gloo/releases/download/v1.2.10/glooctl-linux-amd64; chmod +x glooctl-linux-amd64; mv glooctl-linux-amd64 ~/bin
$ glooctl install knative
$ kubectl get pods -n knative-serving
NAME READY STATUS RESTARTS AGE
activator-77fc555665-rvrst 1/1 Running 0 2m23s
autoscaler-5c98b7c9b6-x8hh4 1/1 Running 0 2m21s
autoscaler-hpa-5cfd4f6845-w87kq 1/1 Running 0 2m22s
controller-7fd74c8f67-tprm8 1/1 Running 0 2m19s
webhook-74847bb77c-txr2g 1/1 Running 0 2m17s
$ kubectl get pods -n gloo-system
NAME READY STATUS RESTARTS AGE
discovery-859d7fbc9c-8xhvh 1/1 Running 0 51s
gloo-545886d9c6-85mwt 1/1 Running 0 51s
ingress-67d4996d75-lkkmw 1/1 Running 0 50s
knative-external-proxy-767dfd656c-wwv2z 1/1 Running 0 50s
knative-internal-proxy-6fdddcc6b5-7vqd8 1/1 Running 0 51s
Bouwe en útfiere OpenWhisk boppe op Knative
- It krijen fan de ynhâld :
$ git clone https://github.com/tektoncd/catalog/
$ cd catalog/openwhisk- Wy sette de gegevens foar tagong ta it register as omjouwingsfariabelen en bewarje se as in Kubernetes-geheim:
$ export DOCKER_USERNAME=<your docker hub username>
$ export DOCKER_PASSWORD=<your docker hub password>
$ sed -e 's/${DOCKER_USERNAME}/'"$DOCKER_USERNAME"'/' -e 's/${DOCKER_PASSWORD}/'"$DOCKER_PASSWORD"'/' docker-secret.yaml.tmpl > docker-secret.yaml
$ kubectl apply -f docker-secret.yamlWy kontrolearje:
$ kubectl get secret
NAME TYPE DATA AGE
dockerhub-user-pass kubernetes.io/basic-auth 2 21s- Meitsje in akkount foar bouwomjouwings:
$ kubectl apply -f service-account.yamlWy kontrolearje:
$ kubectl get serviceaccount/openwhisk-runtime-builder
NAME SECRETS AGE
openwhisk-runtime-builder 2 31m- Meitsje in taak om in ôfbylding te bouwen foar OpenWhisk
$ kubectl apply -f openwhisk.yaml
task.tekton.dev/openwhisk created- Wy rinne de taak om de ôfbylding te bouwen (mei NodeJS as foarbyld):
Meitsje in taskrun.yaml-bestân mei de ynhâld:
# Git Pipeline Resource for OpenWhisk NodeJS Runtime
apiVersion: tekton.dev/v1alpha1
kind: PipelineResource
metadata:
name: openwhisk-nodejs-runtime-git
spec:
type: git
params:
- name: revision
value: master
- name: url
value: https://github.com/apache/openwhisk-runtime-nodejs.git
---
# Image Pipeline Resource for OpenWhisk NodeJS Sample Application
apiVersion: tekton.dev/v1alpha1
kind: PipelineResource
metadata:
name: openwhisk-nodejs-helloworld-image
spec:
type: image
params:
- name: url
value: docker.io/${DOCKER_USERNAME}/openwhisk-nodejs-helloworld
---
# Task Run to build NodeJS image with the action source
apiVersion: tekton.dev/v1alpha1
kind: TaskRun
metadata:
name: openwhisk-nodejs-helloworld
spec:
serviceAccountName: openwhisk-runtime-builder
taskRef:
name: openwhisk
inputs:
resources:
- name: runtime-git
resourceRef:
name: openwhisk-nodejs-runtime-git
params:
- name: DOCKERFILE
value: "./runtime-git/core/nodejs10Action/knative/Dockerfile"
- name: OW_ACTION_NAME
value: "nodejs-helloworld"
- name: OW_ACTION_CODE
value: "function main() {return {payload: 'Hello World!'};}"
- name: OW_PROJECT_URL
value: ""
outputs:
resources:
- name: runtime-image
resourceRef:
name: openwhisk-nodejs-helloworld-image
---Wy tapasse de hjoeddeistige gegevens foar dit bestân:
$ sed 's/${DOCKER_USERNAME}/'"$DOCKER_USERNAME"'/' -i taskrun.yamlWy jilde:
$ kubectl apply -f taskrun.yaml
pipelineresource.tekton.dev/openwhisk-nodejs-runtime-git created
pipelineresource.tekton.dev/openwhisk-nodejs-helloworld-image created
taskrun.tekton.dev/openwhisk-nodejs-helloworld createdIt kontrolearjen fan it wurk bestiet út it krijen fan de namme fan de pod en it besjen fan syn status. Jo kinne ek it útfieringslogboek fan elke stap besjen, bygelyks:
$ kubectl get taskrun
NAME SUCCEEDED REASON STARTTIME COMPLETIONTIME
openwhisk-nodejs-helloworld True Succeeded 5m15s 44s
$ kubectl get pod openwhisk-nodejs-helloworld-pod-4640d3
NAME READY STATUS RESTARTS AGE
openwhisk-nodejs-helloworld-pod-4640d3 0/6 Completed 0 5m20s
$ kubectl logs openwhisk-nodejs-helloworld-pod-4640d3 -c step-git-source-openwhisk-nodejs-runtime-git-r8vhr
{"level":"info","ts":1576532931.5880227,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: open /var/run/ko/refs/heads/master: no such file or directory"}
{"level":"info","ts":1576532936.538926,"logger":"fallback-logger","caller":"git/git.go:81","msg":"Successfully cloned https://github.com/apache/openwhisk-runtime-nodejs.git @ master in path /workspace/runtime-git"}
{"level":"warn","ts":1576532936.5395331,"logger":"fallback-logger","caller":"git/git.go:128","msg":"Unexpected error: creating symlink: symlink /tekton/home/.ssh /root/.ssh: file exists"}
{"level":"info","ts":1576532936.8202565,"logger":"fallback-logger","caller":"git/git.go:109","msg":"Successfully initialized and updated submodules in path /workspace/runtime-git"}Nei útfiering sille wy in ôfbylding hawwe yn 'e Registry dy't kin wurde ynset mei it kn-hulpprogramma, ûntworpen om te wurkjen mei Knative tsjinsten, bygelyks:
kn service create nodejs-helloworld --image docker.io/${DOCKER_USERNAME}/openwhisk-nodejs-helloworld
Service 'nodejs-helloworld' successfully created in namespace 'default'.
Waiting for service 'nodejs-helloworld' to become ready ... OK
Service URL:
http://nodejs-helloworld.default.example.comAs jo Gloo brûke, kinne jo de funksjonaliteit sa kontrolearje:
$ curl -H "Host: nodejs-helloworld.default.example.com" -X POST $(glooctl proxy url --name knative-external-proxy)
{"OK":true}
$ curl -H "Host: nodejs-helloworld.default.example.com" -X POST $(glooctl proxy url --name knative-external-proxy)
{"payload":"Hello World!"}Oare artikels yn 'e rige
Boarne: www.habr.com