Lesi sihloko siphetha uchungechunge lwamanothi ahunyushwe mayelana ne-OpenWhisk avela kumbhali . Namuhla sizobheka inqubo yokukhipha i-OpenWhisk phezu kwe-Kubernetes ngemiyalo elungisiwe ukuze isebenze nezinguqulo zamanje zezinhlelo zokusebenza. Izophinde ihlanganise inqubo yokusebenzisa imisebenzi ye-OpenWhisk kusetshenziswa i-Knative ne-TektonCD ku-Kubernetes kusetshenziswa isikhathi sokusebenza se-Nodejs.
Isebenzisa i-OpenWhisk ku-Kubernetes
Ngokuhamba kwezinsuku ezimbalwa, ngizame ukusebenzisa i-OpenWhisk ku-Kubernetes ukuze ngidale indawo yokuhlola elula nesheshayo. Futhi njengoba ngimusha ku-Kubernetes, ngikholwa ukuthi kusetshenziswe usuku nengxenye ekuthunyelweni okuyimpumelelo. IN Amakhosombe anemiyalo ecace kakhulu yokukhipha i-OpenWhisk ku-Kubernetes. Nansi imiyalo yokusebenzisa eyenzelwe i-Mac (Ngizokwenza konke ku-Linux ngoba ngikhetha i-Linux. - cishe. umhumushi).
- Ifaka isiphathi sephakheji
asdf, ngemva kwalokho silungisa ngokuzenzakalelayo~/.bash_profilenoma okufana nalokhu:
$ brew install asdf
$ [ -s "/usr/local/opt/asdf/asdf.sh" ] && . /usr/local/opt/asdf/asdf.sh
$ source ~/.bash_profile- Yengeza ama-plugin
minikubeиkubelet:
$ asdf plugin-add kubectl
$ asdf plugin-add minikube- Faka i-minikube ne-kubelet:
$ asdf install kubectl 1.9.0
$ asdf global kubectl 1.9.0
$ asdf install minikube 0.25.2
$ asdf global minikube 0.25.2Ku-Linux, lesi sinyathelo senziwa into efana nale (yonke into ifakwa ~/bin, esohlwini INDLELA yami, inothi lomhumushi):
$ 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/- Dala umshini we-minikube virtual (i-VirtualBox kumele ifakwe kuqala):
$ minikube start --cpus 2 --memory 4096 --kubernetes-version=v1.9.0 --extra-config=apiserver.Authorization.Mode=RBACminikube start , ngaphandle kwamapharamitha namanani azenzakalelayo. - cishe. umhumushi]
$ 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"- Ukushintsha inethiwekhi ku-Docker iye kumodi yokuziphatha okubi:
$ minikube ssh -- sudo ip link set docker0 promisc on- Dala indawo yamagama bese umaka inodi yesisebenzi:
$ kubectl create namespace openwhisk
$ kubectl label nodes --all openwhisk-role=invoker- Sithola okuqukethwe kwendawo yokugcina futhi sibhala ngaphezulu uhlobo lokungena kufayela le-mycluster.yaml:
$ 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- Faka i-Helm futhi uyisebenzise usebenzisa:
$ 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- Sihlola ukuthi yonke into ikhuphukile (STATUS = Iyasebenza noma Iqediwe):
$ 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- Ilungiselela i-wsk ukuze isebenze:
$ wsk property set --apihost 192.168.99.100:31001
$ wsk property set --auth 23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwPSihlola:
$ wsk -i list
Entities in namespace: default
packages
actions
triggers
rulesIzinkinga nezixazululo zazo
getsockopt: uxhumano lunqatshiwe
$ 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 refusedIhlola ukuthi iziqukathi zisendaweni yamagama openwhisk esimweni Running, ngoba kwesinye isikhathi ishayisana namaphutha CreateContainerConfigError.
Umfakisicelo usaqalisa — Init:1/2
Inqubo yokulanda izindawo ezihlukahlukene zesikhathi sokusebenza ingathatha isikhathi eside. Ukusheshisa izinto, ungacacisa ubuncane obuncane obufushanisiwe kufayela mycluster.yaml:
whisk:
runtimes: "runtimes-minimal-travis.json"Isitsha esinegama -faka-amaphakheji- iphahlazeka kuphutha
Vele wandise isikhathi sokuvala sokuhlolwa kokuphila.
Ukufaka i-OpenWhisk phezu kwe-Knative
U-Priti Desai wenze ukufakwa phezulu kweqoqo efwini le-IBM, kanye ne-minikube evamile, esebenzisa i-Knative Build and BuildTemplates. Ngizophinde ngifake phezu kwe-minukube, ngokusekelwe ekutheni kanjani kubhulogi yethu ngaphambilini - usebenzisa izinguqulo zesofthiwe zakamuva. Njengoba i-Knative Build and BuildTemplates yehlisiwe ngokusemthethweni, ngizosebenzisa ukumiselela okunconyiwe ngendlela ye-Tekton Pipelines. Esinye isihloko sabhalwa ngemva kokufunda imibhalo ye-Tekton Pipelines, kodwa sisekelwe emibonweni kaPriti. Ukuze usebenze, uzodinga ukufinyelela kwe-Docker Registry - mina, njengombhali wokuqala, ngizosebenzisa i-DockerHub.
$ 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
Ukwakha nokusebenzisa i-OpenWhisk phezulu kwe-Knative
- Ukuthola okuqukethwe :
$ git clone https://github.com/tektoncd/catalog/
$ cd catalog/openwhisk- Setha idatha yokufinyelela ku-Registry njengokuguquguquka kwemvelo futhi siyilondoloze njengemfihlo ye-Kubernetes:
$ 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.yamlSihlola:
$ kubectl get secret
NAME TYPE DATA AGE
dockerhub-user-pass kubernetes.io/basic-auth 2 21s- Dala i-akhawunti yezindawo zokwakha:
$ kubectl apply -f service-account.yamlSihlola:
$ kubectl get serviceaccount/openwhisk-runtime-builder
NAME SECRETS AGE
openwhisk-runtime-builder 2 31m- Dala umsebenzi wokwakha isithombe se-OpenWhisk
$ kubectl apply -f openwhisk.yaml
task.tekton.dev/openwhisk created- Senza umsebenzi wokwakha isithombe (sisebenzisa i-NodeJS njengesibonelo):
Dala ifayela le-taskrun.yaml nokuqukethwe:
# 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
---Sisebenzisa idatha yamanje yaleli fayela:
$ sed 's/${DOCKER_USERNAME}/'"$DOCKER_USERNAME"'/' -i taskrun.yamlSifaka isicelo:
$ 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 createdUkuhlola umsebenzi kuhlanganisa ukuthola igama le-pod nokubuka isimo sayo. Ungaphinda ubuke ilogu yokusebenza yesinyathelo ngasinye, isibonelo:
$ 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"}Ngemva kokubulawa, sizoba nesithombe kuRegistry esingasatshalaliswa kusetshenziswa insiza ye-kn, eklanyelwe ukusebenza nezinsizakalo ze-Knative, isibonelo:
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.comUma usebenzisa i-Gloo, ungabheka ukusebenza kwayo kanje:
$ 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!"}Ezinye izihloko ochungechungeni
Source: www.habr.com