Maqaalkani wuxuu soo afjarayaa qoraallada taxanaha ah ee OpenWhisk ee qoraaga la turjumay . Maanta waxaan eegi doonaa habka loo daabulo OpenWhisk dul Kubernetes oo wata amarada la saxay si ay ula shaqeeyaan noocyada codsiyada hadda. Waxay sidoo kale dabooli doontaa habka socodsiinta hawlaha OpenWhisk iyadoo la adeegsanayo Knative iyo TektonCD ee Kubernetes iyadoo la adeegsanayo Nodejs runtime.
Gelinaya OpenWhisk Kubernetes
Dhowr maalmood gudahood, waxaan tijaabiyay inaan OpenWhisk geeyo Kubernetes si aan u abuuro goob tijaabo ah oo fudud oo degdeg ah. Oo maadaama aan ku cusubahay Kubernetes, waxaan aaminsanahay in maalin iyo badh lagu kharash gareeyay keenista guul leh. IN Kaydyadu waxay leeyihiin tilmaamo aad u cad oo lagu geynayo OpenWhisk Kubernetes. Waa kuwan tilmaamaha geynta loo sameeyay Mac (Sidoo kale wax walba waan sameyn doonaa Linux, sababtoo ah waxaan doorbidaa Linux. - qiyaastii. turjumaan).
- Rakibaadda maareeyaha xirmada
asdf, ka dib markaa si toos ah ayaanu u saxnaa~/.bash_profileama u dhiganta sidan:
$ brew install asdf
$ [ -s "/usr/local/opt/asdf/asdf.sh" ] && . /usr/local/opt/asdf/asdf.sh
$ source ~/.bash_profile[In Linux Tallaabadan looma baahna, inkastoo la heli karo. - qiyaastii. turjumaan]
- Ku darida plugins
minikubeиkubelet:
$ asdf plugin-add kubectl
$ asdf plugin-add minikube[Mar labaad, waan ka boodnaa tallaabadan Linux. - qiyaastii. turjumaan]
- Ku rakib minikube iyo 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[Noocyo gaar ah ayaa la rakibay, laakiin waxaan hubiyay wax walba oo ku saabsan noocyadii ugu dambeeyay ee la heli karo Linux; Waxaan u maleynayaa inaad si ammaan ah u rakibi karto kii ugu dambeeyay. - qiyaastii. turjumaan]
In Linux Tallaabadan waxaa la sameeyaa wax sidan oo kale ah (wax walba waxaa lagu rakibay ~/bin, kaas oo ku jira PATH-kayga, qoraalka turjumaanka):
$ 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/- Abuur mishiinka farsamada gacanta ee minikube (VirtualBox waa in horay loo sii rakibaa):
$ minikube start --cpus 2 --memory 4096 --kubernetes-version=v1.9.0 --extra-config=apiserver.Authorization.Mode=RBAC[Wax walba waxay la shaqeeyaan kooxdayda minikube start , iyada oo aan lahayn xuduudo iyo qiimeyaal aan caadi ahayn. - qiyaastii. turjumaan]
$ 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"- U beddelashada shabakada Docker una beddesho qaab sinaysta:
$ minikube ssh -- sudo ip link set docker0 promisc on- Samee meel magac oo calaamadee noodhka shaqaalaha:
$ kubectl create namespace openwhisk
$ kubectl label nodes --all openwhisk-role=invoker- Waxaan helnaa waxa ku jira kaydka oo aan ka gudubno nooca soo galitaanka faylka 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- Ku rakib Helm oo ku dheji adigoo isticmaalaya:
$ 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[In Linux Iyada oo la adeegsanayo noocyadii ugu dambeeyay (v3.0.1 ayaa la heli karay) waxay noqon doontaa wax yar oo ka duwan. - qiyaastii. turjumaan]
$ 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- Waxaan hubinaa in wax walba kor u kaceen ( XAALADDA = Socod ama Dhammaystiran):
$ 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- Isku habeynta wsk si ay u shaqeyso:
$ wsk property set --apihost 192.168.99.100:31001
$ wsk property set --auth 23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwPHubinta:
$ wsk -i list
Entities in namespace: default
packages
actions
triggers
rulesDhibaatooyinka iyo xalkooda
getsockot: xiriirku wuu diiday
$ 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 refusedHubinta in weelashu ku jiraan meesha magaca openwhisk meeqaam Running, sababtoo ah mararka qaarkood waxay ku dhacdaa khaladaad CreateContainerConfigError.
Soo wacaha ayaa wali bilaabaya - Init: 1/2
Habka soo dejinta deegaan runtime kala duwan waxay qaadan kartaa waqti dheer. Si wax loo dedejiyo, waxaad ku qeexi kartaa liiska ugu yar ee la soo gaabiyay faylka mycluster.yaml:
whisk:
runtimes: "runtimes-minimal-travis.json"Weel magac leh baakadaha ku rakib- shil ku dhaco Khalad
Kaliya kordhi wakhtiga dhimista ee imtixaanada nolosha.
Ku rakibida OpenWhisk dusha Knative
Priti Desai waxay ku rakibtay dusha sare ee kutlada daruuraha IBM, iyo sidoo kale minikube caadi ah, iyadoo adeegsanaysa Knative Build and BuildTemplates. Waxaan sidoo kale ku rakibi doonaa korka minukube, oo ku saleysan sida In blog-ka hore - iyadoo la isticmaalayo noocyadii ugu dambeeyay ee software. Maadaama Knative Build and BuildTemplates si rasmi ah loo joojiyay, waxaan isticmaali doonaa beddelka lagu taliyey ee qaabka Tekton Pipelines. Maqaalka intiisa kale waxaa la qoray ka dib markii la akhriyay dukumentiyada Tekton Pipelines, laakiin waxay ku salaysan tahay fikradaha Priti. Si aad u shaqeyso, waxaad u baahan doontaa marin u helka qaar ka mid ah Diiwaanka Docker-Aniga, sida qoraaga asalka ah, waxaan isticmaali doonaa 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
Ku dhis oo ku socodsiiya OpenWhisk dusha sare ee Knative
- Helitaanka waxa ku jira :
$ git clone https://github.com/tektoncd/catalog/
$ cd catalog/openwhisk- Waxaan u dejinay xogta gelitaanka Diiwaanka sida doorsoomayaasha deegaanka waxaana u kaydinay sirta 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.yamlHubinta:
$ kubectl get secret
NAME TYPE DATA AGE
dockerhub-user-pass kubernetes.io/basic-auth 2 21s- U samee koontada dhismaha deegaanka:
$ kubectl apply -f service-account.yamlHubinta:
$ kubectl get serviceaccount/openwhisk-runtime-builder
NAME SECRETS AGE
openwhisk-runtime-builder 2 31m- U samee hawl si aad sawirka ugu dhisto OpenWhisk
$ kubectl apply -f openwhisk.yaml
task.tekton.dev/openwhisk created- Waxaan wadnaa hawsha si aan u dhisno sawirka (iyadoo la adeegsanayo NodeJS tusaale ahaan):
Samee faylka taskrun.yaml oo wata waxa ku jira:
# 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
---Waxaan u isticmaalnaa xogta hadda jirta faylkan:
$ sed 's/${DOCKER_USERNAME}/'"$DOCKER_USERNAME"'/' -i taskrun.yamlWaxaan codsaneynaa:
$ 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 createdHubinta shaqadu waxay ka kooban tahay helida magaca boodhka oo la eego xaaladdeeda. Waxa kale oo aad arki kartaa diiwaanka fulinta tallaabo kasta, tusaale ahaan:
$ 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"}Dilka ka dib, waxa aanu ku yeelan doonaa sawirka Diiwaanka oo la geyn karo iyadoo la isticmaalayo kn utility, looguna talagalay in lagula shaqeeyo adeegyada Knative, tusaale ahaan:
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.comHaddii aad isticmaasho Gloo, waxaad hubin kartaa sida ay u shaqeyso:
$ 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!"}Maqaallada kale ee taxanaha ah
Source: www.habr.com
