Wannan labarin ya ƙare jerin bayanan da aka fassara game da OpenWhisk daga marubucin Priti Desai. A yau za mu kalli tsarin tura OpenWhisk akan Kubernetes tare da ingantattun umarni don aiki tare da nau'ikan aikace-aikacen yanzu. Hakanan zai rufe tsarin gudanar da ayyukan OpenWhisk ta amfani da Knative da TektonCD akan Kubernetes ta amfani da lokacin aikin Nodejs.
Ana tura OpenWhisk akan Kubernetes
A cikin ƴan kwanaki, na gwada tare da tura OpenWhisk zuwa Kubernetes don ƙirƙirar filin gwaji mai sauƙi da sauri. Kuma tun da nake sabon zuwa Kubernetes, na yi imani cewa an kashe kwana ɗaya da rabi a cikin nasarar turawa. IN wannan Ma'ajiyar ajiyar suna da cikakkun umarni don tura OpenWhisk akan Kubernetes. Anan ga umarnin turawa da aka yi don Mac (Zan kuma yi komai akan Linux saboda na fi son Linux. - kimanin. fassara).
Sanya manajan kunshin asdf, bayan haka muna gyara ta atomatik ~/.bash_profile ko makamancinsa kamar haka:
[Hakanan, tsallake wannan matakin akan Linux. - kimanin. mai fassara]
Sanya minikube da kubelet:
$ asdf install kubectl 1.9.0
$ asdf global kubectl 1.9.0
$ asdf install minikube 0.25.2
$ asdf global minikube 0.25.2
[an shigar da takamaiman nau'ikan, amma na duba komai akan sabbin nau'ikan da aka samu na Linux; Ina tsammanin za ku iya shigar da na baya-bayan nan lafiya. - kimanin. mai fassara]
A Linux, ana yin wannan matakin wani abu kamar wannan (ana saka komai a ~/bin, wanda aka jera a cikin PATH na, bayanin mai fassara):
$ 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
[A Linux tare da sabbin nau'ikan (v3.0.1 yana samuwa) zai ɗan bambanta. - kimanin. mai fassara]
$ wsk property set --apihost 192.168.99.100:31001
$ wsk property set --auth 23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP
Binciken:
$ wsk -i list
Entities in namespace: default
packages
actions
triggers
rules
Matsaloli da hanyoyin magance su
getsockot: haɗin ya ƙi
$ 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 refused
Dubawa cewa kwantena suna cikin sararin sunan openwhisk cikin hali Running, saboda wani lokacin yakan yi karo da kurakurai CreateContainerConfigError.
Mai kira har yanzu yana farawa - Init: 1/2
Tsarin zazzage mahallin runtime daban-daban na iya ɗaukar lokaci mai tsawo. Don hanzarta abubuwa, zaku iya ƙayyade mafi ƙarancin jeri a cikin fayil ɗin mycluster.yaml:
whisk:
runtimes: "runtimes-minimal-travis.json"
Kwantena mai suna -shigar-kunki- ya yi karo da Kuskure
Kawai ƙara ƙarewar lokacin gwajin rayuwa.
Sanya OpenWhisk akan Knative
Priti Desai ta aiwatar da shigarwa a saman gungu a cikin gajimare na IBM, da kuma kan minikube na yau da kullun, ta amfani da Knative Build and BuildTemplates. Zan kuma shigar a saman minukube, bisa ga yadda aka kwatanta a cikin blog ɗin mu a baya - ta amfani da sabbin nau'ikan software. Tun da Knative Build da BuildTemplates an soke bisa hukuma, zan yi amfani da shawarar maye gurbin ta hanyar Tekton Pipelines. An rubuta sauran labarin bayan karanta takaddun don Tekton Pipelines, amma ya dogara ne akan ra'ayoyin Priti. Don yin aiki, kuna buƙatar samun dama ga wasu Docker Registry - Ni, kamar marubucin asali, zan yi amfani da DockerHub.
$ sed 's/${DOCKER_USERNAME}/'"$DOCKER_USERNAME"'/' -i taskrun.yaml
Muna nema:
$ 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 created
Duba aikin ya ƙunshi samun sunan kwaf ɗin da duba matsayinsa. Hakanan zaka iya duba log ɗin aiwatarwa na kowane mataki, misali:
$ 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"}
Bayan aiwatarwa, za mu sami hoto a cikin Registry wanda za'a iya tura shi ta amfani da kayan aikin kn, wanda aka tsara don aiki tare da sabis na Knative, misali:
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.com
Idan kuna amfani da Gloo, zaku iya duba ayyukanta kamar haka: