Eminyakeni engu-25 edlule, i-Java yangena ohlelweni olujwayelekile futhi ekugcineni yaba enye yezinto ezibalulekile okwakhiwa kuzo izitaki zezinhlelo zokusebenza. Nokho, namuhla, abantu abaningi nezinhlangano eziye zathembeka ku-Java iminyaka eminingi zimatasa ziyafuduka noma zicabangela ukuthuthela endaweni yesikhulumi. noma okuphuma kuyo njenge noma .
Ngeshwa, i-Kubernetes inejika lokufunda eliwumqansa futhi yethula esinye isendlalelo sokusebenza enqubweni yokuthuthukisa abahleli bezinhlelo ze-Java abayijwayele. Namuhla sizokutshela ukuthi ungayisebenzisa kanjani , ukwenza lula le misebenzi eyengeziwe ehlotshaniswa ne-Kubernetes neziqukathi, nokuqinisekisa ukuthuthela okungenabuhlungu kuplathifomu yamafu kuyilapho kugcinwa i-ecosystem ye-Java ejwayelekile. Ngaphezu kwalokho, sizobonisa ukuthi zifakwa kanjani izinhlelo zokusebenza ze-Java endaweni yesikhulumi se-OpenShift kusetshenziswa i-OpenShift Maven plugin.
Inqubo Yendabuko Yokuthuthukiswa Kwe-Java
Inqubo yokuthuthukiswa kwendabuko (Umfanekiso 1) ubandakanya ikhodi yokubhala kanjiniyela, bese udala amayunithi okuthunyelwa ngendlela ye-JAR noma amafayela e-WAR, bese ikhipha nokusebenzisa lawa mafayela kuwebhu noma iseva yohlelo lokusebenza. Indlela eyinhloko yokwenza lokhu ukusebenzisa i-Maven kusukela kulayini womyalo noma usebenzise i-IDE efana ne-IntelliJ noma i-Eclipse ukuze ukhode futhi uhlanganise izinhlelo zokusebenza. Onjiniyela basetshenziselwa ukwenza izinguquko zekhodi futhi bahlole yonke into kahle ngaphambi kokwenza ikhodi futhi bayihambise ekulawuleni inguqulo.
Ilayisi. 1. Inqubo yokuthuthukiswa kwe-Java yendabuko.
Inqubo Yokuthuthukisa i-Java Yefu
Lapho uthuthela kuzinhlelo zokusebenza zefu, Kubernetes kanye . Ngakho-ke, manje umthuthukisi udinga ukupakisha izinhlelo zokusebenza ze-Java futhi udale ama-Kubernetes abonisa lezi zithombe. Lezi zibonakaliso zibe sezisetshenziswa kuseva yokukhiqiza esebenzisa i-Kubernetes. Ngokulandelayo, u-Kubernetes uthatha lezi zithombe endaweni yokubhalisa bese esebenzisa izinhlelo zokusebenza ngokuvumelana nokuhlelwa esikubhale kuma-manifest, ngokuvamile okungamafayela e-YAML.
I-metamorphosis yenqubo yendabuko yokuthuthukiswa kwe-Java ekushintsheleni emafini kuboniswa ku-Fig. 2.
Ilayisi. 2. Inqubo yokuthuthukisa i-Java yamafu.
Eclipse JKube
Ukuthuthela e-Kubernetes kunezela esinye isendlalelo sokusebenza ohlelweni lokuthuthukisa, futhi abathuthukisi abaningi banovalo ngakho ngoba bafuna ukugxila emsebenzini wabo oyinhloko—umqondo wohlelo lokusebenza—kunokuba basetshenziswe kanjani. Futhi kulapho kungena khona. , okuvumela abathuthukisi ukuthi basebenzise imitapo yolwazi yabo nama-plugin ( kanye noma ) ukwenza kalula isiqukathi kanye nemisebenzi ehlobene ne-Kubernetes ngokulandela umdwebo osesithombeni. 2.
Kuso sonke lesi sihloko, sizokukhombisa ukuthi ungayenza kanjani ibe lula inqubo yokuthuthukisa i-Java endaweni ye-Kubernetes ngokusebenzisa i-Eclipse JKube nge-Kubernetes Maven Plugin.
I-Cloud Development Process Ukusebenzisa i-Eclipse JKube
Ake sicabangele isikimu sokuthuthukiswa kwe-Java esishintshwe kancane sefu kusukela ku-Fig. 2, esethula i-Eclipse JKube ne-Kubernetes Maven Plugin kuso, njengoba kuboniswe ku-Fig. 3.
Ilayisi. 3. Inqubo yokuthuthukisa i-Java yefu isebenzisa i-Eclipse JKube.
Njengoba sibona, lapha yonke imisebenzi yokusebenzelana ne-Kubernetes neziqukathi (ezigqanyiswe ngokubomvu kumdwebo) zithathelwa indawo imisebenzi yegoli ye-Eclipse JKube ezenzakalelayo, esohlwini Lwethebula. 1.
Ithebula 1. Imisebenzi ezenzakalelayo ye-Eclipse JKube.
Inhloso
Isiteji
Incazelo
PRE_INTEGRATION_TEST
Ukwakha izithombe zedokhu
FAKA
Ilayisha izithombe ze-docker endaweni yokubhalisa
PROCESS_RESOURCES
Ukukhiqiza ama-K8s abonisa
COMPILE
Ukusebenzisa i-manifest ekhiqiziwe kuma-K8s
UNGASEBENZI
Ukukhipha izinsiza ze-K8s ebezisetshenziswa kusetshenziswa i-k8s:apply ne-k8s:deploy
Qaphela: Uma ungafuni ukuthi imisebenzi isebenzise lokhu okumisiwe okunemibono, ungazilungisela i-Eclipse JKube ngokwakho, njengoba isekela ukucushwa nge- и .
Manje ake sibheke izibonelo zokusebenzisa i-Eclipse JKube ne-Kubernetes Maven Plugin lapho usebenza nezinhlelo zokusebenza.
Kusetshenziswa Uhlelo Lwe-Java ku-Kubernetes Usebenzisa i-Eclipse JKube
Kulesi sibonelo sizosebenzisa uhlelo olulula lwe-Java kuqoqo usebenzisa i-Eclipse JKube. Sisebenzisa i-Kubernetes Maven Plugin, singasetha amapharamitha wokuthumela ngaphandle kokuthi sibhale noma yikuphi ukucushwa.
Njengesibonelo isicelo sisebenzisa , okukhiqiza okukhiphayo kwe-JSON endaweni/ekugcineni okungahleliwe:
~/work/repos/eclipse-jkube-demo-project : $ curl localhost:8080/random | jq .
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 45 0 45 0 0 818 0 --:--:-- --:--:-- --:--:-- 818
{
"id": "e80a4d10-c79b-4b9a-aaac-7c286cb37f3c"
}
Isinyathelo 1. Landa i-Kubernetes Maven Plugin
I-Kubernetes Maven Plugin isendaweni yokugcina izinto . Ukuze usebenzise i-Eclipse JKube udinga ukwengeza i-Kubernetes Maven Plugin ku-pom.xml yakho njengokuncika:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>kubernetes-maven-plugin</artifactId>
<version>${jkube.version}</version>
</plugin>
Uma i-OpenShift isetshenziswa esikhundleni se-Kubernetes emsulwa, lapho-ke i-pom.xml ilungiswa ngale ndlela elandelayo:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>openshift-maven-plugin</artifactId>
<version>${jkube.version}</version>
</plugin>
Isinyathelo sesi-2. Yakha isithombe sedokhu
Ifayela le-JAR lohlelo lokusebenza lingakhiwa ngomyalo wephakheji ye-mvn, bese umsebenzi we-mvn we-mvn k8s:build ungasetshenziswa ukwakha isithombe se-docker sohlelo lokusebenza. Qaphela ukuthi sikhiphe igama lesithombe esimisiwe ngalesi sici:
<jkube.generator.name>docker.io/rohankanojia/random-generator:${project.version}</jkube.generator.name>
Ngaphambi kokwakha isithombe, udinga ukwenza isiqiniseko sokuthi i-docker daemon idalulwa ngendlela efanele. Lokhu kungenziwa ngomyalo olandelayo:
$ eval $(minikube docker-env)
Bese sifaka i-mvn k8s:i-build command, futhi yilokhu esizokubona esikrinini lapho sakha isithombe se-docker sisebenzisa umsebenzi wokwakha we-Eclipse JKube:
~/work/repos/eclipse-jkube-demo-project : $ mvn k8s:build
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< meetup:random-generator >-----------------------
[INFO] Building random-generator 0.0.1
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- kubernetes-maven-plugin:1.0.0-rc-1:build (default-cli) @ random-generator ---
[INFO] k8s: Running in Kubernetes mode
[INFO] k8s: Building Docker image in Kubernetes mode
[INFO] k8s: Running generator spring-boot
[INFO] k8s: spring-boot: Using Docker image quay.io/jkube/jkube-java-binary-s2i:0.0.7 as base / builder
[INFO] k8s: [docker.io/rohankanojia/random-generator:0.0.1] "spring-boot": Created docker-build.tar in 251 milliseconds
[INFO] k8s: [docker.io/rohankanojia/random-generator:0.0.1] "spring-boot": Built image sha256:a20e5
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.053 s
[INFO] Finished at: 2020-08-10T11:28:23+05:30
[INFO] ------------------------------------------------------------------------
~/work/repos/eclipse-jkube-demo-project : $
Isinyathelo sesi-3. Layisha isithombe endaweni yokubhalisa yedokha
Ngemuva kokuthi sakhe isithombe sedokhu esine-push registry emisiwe (kithina i-docker.io), singathumela lesi sithombe ebhukwini. Yilokhu okuzoboniswa ngemuva kokucela u-Eclipse JKube ukuthi enze i-mvn k8s: push push task:
~/work/repos/eclipse-jkube-demo-project : $ mvn k8s:push
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< meetup:random-generator >-----------------------
[INFO] Building random-generator 0.0.1
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- kubernetes-maven-plugin:1.0.0-rc-1:push (default-cli) @ random-generator ---
[INFO] k8s: Running in Kubernetes mode
[INFO] k8s: Building Docker image in Kubernetes mode
[INFO] k8s: Running generator spring-boot
[INFO] k8s: spring-boot: Using Docker image quay.io/jkube/jkube-java-binary-s2i:0.0.7 as base / builder
[INFO] k8s: The push refers to repository [docker.io/rohankanojia/random-generator]
5dcd9556710f: Layer already exists
b7139ad07aa8: Layer already exists
b6f081e4b2b6: Layer already exists
d8e1f35641ac: Layer already exists
[INFO] k8s: 0.0.1: digest: sha256:9f9eda2a13b8cab1d2c9e474248500145fc09e2922fe3735692f9bda4c76002d size: 1162
[INFO] k8s: Pushed docker.io/rohankanojia/random-generator:0.0.1 in 7 seconds
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.222 s
[INFO] Finished at: 2020-08-10T11:35:37+05:30
[INFO] ------------------------------------------------------------------------
~/work/repos/eclipse-jkube-demo-project : $
Ngemva kokuthumela isithombe, udinga ukuhlola ukuthi sifakiwe ebhukwini. Esimweni sethu, sivele siyibona ku-Docker Hub, njengoba kukhonjisiwe ku-Fig. 4.
Ilayisi. 4. Isithombe esithunyelwe kurejista sivele ku-Docker Hub.
Isinyathelo sesi-4. Khiqiza izisetshenziswa ze-Kubernetes zohlelo lokusebenza
Ngakho-ke, siqoqe isithombe sohlelo lokusebenza, manje sidinga ukubhala i-Kubernetes manifests. Ukwenza lokhu, i-Eclipse JKube inomsebenzi okhiqiza izibonisi zensiza eqinile ngokusekelwe kuhlaka oluyisisekelo lwe-Java (, , Vert.x noma okunye). Ungakwazi futhi ukwenza ngendlela oyifisayo i-manifest ngokusebenzisa ifayela lokumisa le-XML futhi ubeke izingcezu ezingavuthiwe (izingcezu ze-manifest yensiza edingekayo) kufolda yohlelo lokusebenza src/main/jkube. Kulesi simo, ukulungiselelwa kwakho kuzolayishwa kuma-manifest akhiqiziwe.
Esibonelweni sethu, sishiya yonke into njengoba injalo, ngakho-ke i-Eclipse JKube ikhiqiza i-manifest yokuthunyelwa okuzenzakalelayo kanye nesevisi enohlobo lwe-ClusterIP. Futhi yilapho kuphela siguqula i-manifest yesevisi ukuze siguqule uhlobo lwesevisi lube yi-NodePort. Ungakwazi ukukhipha ukuziphatha okuzenzakalelayo usebenzisa isici esilandelayo:
<jkube.enricher.jkube-service.type>NodePort</jkube.enricher.jkube-service.type>
Yilokhu okukhiphayo kwesikrini kubukeka ngemuva kokuthi sicele u-Eclipse JKube ukuthi enze i-mvn k8s:umsebenzi wensiza yensiza.
~/work/repos/eclipse-jkube-demo-project : $ mvn k8s:resource
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< meetup:random-generator >-----------------------
[INFO] Building random-generator 0.0.1
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- kubernetes-maven-plugin:1.0.0-rc-1:resource (default-cli) @ random-generator ---
[INFO] k8s: Running generator spring-boot
[INFO] k8s: spring-boot: Using Docker image quay.io/jkube/jkube-java-binary-s2i:0.0.7 as base / builder
[INFO] k8s: jkube-controller: Adding a default Deployment
[INFO] k8s: jkube-service: Adding a default service 'random-generator' with ports [8080]
[INFO] k8s: jkube-healthcheck-spring-boot: Adding readiness probe on port 8080, path='/actuator/health', scheme='HTTP', with initial delay 10 seconds
[INFO] k8s: jkube-healthcheck-spring-boot: Adding liveness probe on port 8080, path='/actuator/health', scheme='HTTP', with initial delay 180 seconds
[INFO] k8s: jkube-revision-history: Adding revision history limit to 2
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.344 s
[INFO] Finished at: 2020-08-10T11:38:11+05:30
[INFO] ------------------------------------------------------------------------
~/work/repos/eclipse-jkube-demo-project : $ ls target/classes/META-INF/jkube/kubernetes
random-generator-deployment.yml random-generator-service.yml
~/work/repos/eclipse-jkube-demo-project : $ cat target/classes/META-INF/jkube/kubernetes/random-generator-deployment.yml | head -n10
---
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
jkube.io/git-url: [email protected]:rohanKanojia/eclipse-jkube-demo-project.git
jkube.io/git-commit: 1ef9ef2ef7a6fcbf8eb64c293f26f9c42d026512
jkube.io/git-branch: master
jkube.io/scm-url: https://github.com/spring-projects/spring-boot/spring-boot-starter-parent/random-generator
jkube.io/scm-tag: HEAD
~/work/repos/eclipse-jkube-demo-project : $
Isinyathelo sesi-5. Hambisa uhlelo lokusebenza kuqoqo le-Kubernetes
Manje sonke sesilungele ukusebenzisa uhlelo lokusebenza: senze isithombe salo futhi sabe sesivela ngokuzenzakalelayo i-manifest yensiza. Manje osekusele ukusebenzisa konke lokhu kuqoqo le-Kubernetes. Ukuze usebenzise uhlelo lokusebenza, ungasebenzisa umyalo we-kubectl apply -f, kodwa i-plugin ingasenzela lokhu. Yilokhu okuzovela esikrinini ngemuva kokucela i-Eclipse JKube ukuthi isebenzise i-mvn k8s: sebenzisa umsebenzi wokusebenza:
~/work/repos/eclipse-jkube-demo-project : $ mvn k8s:apply
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< meetup:random-generator >-----------------------
[INFO] Building random-generator 0.0.1
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- kubernetes-maven-plugin:1.0.0-rc-1:apply (default-cli) @ random-generator ---
[INFO] k8s: Using Kubernetes at https://192.168.39.145:8443/ in namespace default with manifest /home/rohaan/work/repos/eclipse-jkube-demo-project/target/classes/META-INF/jkube/kubernetes.yml
[INFO] k8s: Using namespace: default
[INFO] k8s: Creating a Service from kubernetes.yml namespace default name random-generator
[INFO] k8s: Created Service: target/jkube/applyJson/default/service-random-generator.json
[INFO] k8s: Creating a Deployment from kubernetes.yml namespace default name random-generator
[INFO] k8s: Created Deployment: target/jkube/applyJson/default/deployment-random-generator.json
[INFO] k8s: HINT: Use the command `kubectl get pods -w` to watch your pods start up
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.306 s
[INFO] Finished at: 2020-08-10T11:40:57+05:30
[INFO] ------------------------------------------------------------------------
~/work/repos/eclipse-jkube-demo-project : $ kubectl get pods -w
NAME READY STATUS RESTARTS AGE
random-generator-58b7847d7f-9m9df 0/1 Running 0 7s
random-generator-58b7847d7f-9m9df 1/1 Running 0 17s
^C~/work/repos/eclipse-jkube-demo-project : $ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
io-openliberty-sample-getting-started NodePort 10.110.4.104 <none> 9080:30570/TCP 44h
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 18d
random-generator NodePort 10.97.172.147 <none> 8080:32186/TCP 22s
~/work/repos/eclipse-jkube-demo-project : $ curl `minikube ip`:32186/random | jq .
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 45 0 45 0 0 1800 0 --:--:-- --:--:-- --:--:-- 1875
{
"id": "42e5571f-a20f-44b3-8184-370356581d10"
}
Isinyathelo sesi-6. Yehlisa ukusetshenziswa kwezinhlelo zokusebenza kuqoqo le-Kubernetes
Ukuze wenze lokhu, kusetshenziswa umsebenzi ongasetshenzisiwe, ovele ukhiphe zonke izinsiza ezisetshenziswe esinyathelweni sangaphambilini, okungukuthi, lapho umsebenzi wokufaka isicelo wenziwe. Yilokhu esizokubona esikrinini ngemuva kokucela u-Eclipse JKube ukuthi enze umsebenzi we-mvn k8s:undeploy undeploy:
~/work/repos/eclipse-jkube-demo-project : $ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/random-generator-58b7847d7f-9m9df 1/1 Running 0 5m21s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 18d
service/random-generator NodePort 10.97.172.147 <none> 8080:32186/TCP 5m21s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/random-generator 1/1 1 1 5m21s
NAME DESIRED CURRENT READY AGE
replicaset.apps/random-generator-58b7847d7f 1 1 1 5m21s
~/work/repos/eclipse-jkube-demo-project : $ mvn k8s:undeploy
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< meetup:random-generator >-----------------------
[INFO] Building random-generator 0.0.1
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- kubernetes-maven-plugin:1.0.0-rc-1:undeploy (default-cli) @ random-generator ---
[INFO] k8s: Using Kubernetes at https://192.168.39.145:8443/ in namespace default with manifest /home/rohaan/work/repos/eclipse-jkube-demo-project/target/classes/META-INF/jkube/kubernetes.yml
[INFO] k8s: Using namespace: default
[INFO] k8s: Deleting resource Deployment default/random-generator
[INFO] k8s: Deleting resource Service default/random-generator
[INFO] k8s: HINT: Use the command `kubectl get pods -w` to watch your pods start up
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.412 s
[INFO] Finished at: 2020-08-10T11:46:22+05:30
[INFO] ------------------------------------------------------------------------
~/work/repos/eclipse-jkube-demo-project : $ kubectl get pods -w
^C~/work/repos/eclipse-jkube-demo-project : $ kubectl get all
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 18d
~/work/repos/eclipse-jkube-demo-project : $
Yini enye ongayenza nge-Eclipse JKube
Ngakho-ke, sibheke imisebenzi yenhloso eyinhloko ye-Eclipse JKube kanye ne-Kubernetes Maven Plugin, esiza ukuthuthukiswa kwezinhlelo zokusebenza ze-Java ze-platform ye-Kubernetes. Uma ungafuni ukufaka njalo le misebenzi kusuka kukhibhodi, ungayibhala ekucushweni kwe-plugin, isibonelo, kanje:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>kubernetes-maven-plugin</artifactId>
<version>${project.version}</version>
<executions>
<execution>
<goals>
<goal>build</goal>
<goal>resource</goal>
<goal>apply</goal>
</goals>
</execution>
</executions>
</plugin>
Kumelwe kushiwo ukuthi kulesi sihloko asizange sicabangele yonke imisebenzi yezinhloso eku-Eclipse JKube kanye ne-Kubernetes Maven Plugin, ngakho-ke sinikeza kuThebula lesi-2 uhlu lwemisebenzi eyengeziwe engase ibe usizo kuwe.
Ithebula 2. Imisebenzi yegoli eyengeziwe ye-Eclipse JKube.
Inhloso
Isiteji
Incazelo
VALIDATE
Ukuthola amalogi kusuka kuhlelo lokusebenza olusebenza ku-Kubernetes.
PACKAGE
Vula imbobo yokususa iphutha ukuze ukwazi ukususa iphutha kuhlelo lwakho lokusebenza olusebenza ku-Kubernetes usuka ngqo ku-IDE.
FAKA
Ukudala imfoloko yomsebenzi Faka nokusebenzisa i-manifest ekhiqiziwe kuqoqo le-Kubernetes ngendlela efanayo nasesimweni somsebenzi wokufaka isicelo.
PACKAGE
Ukuthunyelwa okuzenzakalelayo okushisayo kohlelo lokusebenza ngokulandelela indawo yalo yegama.
Kusetshenziswa izinhlelo zokusebenza ze-Java ku-Red Hat OpenShift Kusetshenziswa i-OpenShift Maven Plugin
Ukuze sikhiphe uhlelo lokusebenza esibonelweni sethu ku-OpenShift yesigqoko esibomvu, sisebenzisa i-plugin . Umehluko kuphela kuzoba ukuthi isiqalo somsebenzi sizoshintsha sisuka ku-k8s siye ku-oc. Ngokuzenzakalelayo i-plugin ye-Kubernetes Maven iyakwenza -assemblies, kanye ne-OpenShift Maven plugin - imihlangano . Asenzi noma yiziphi izinguquko kuphrojekthi yethu ngaphandle kokukhipha impahla ye-jkube.generator.name njengoba ingadingeki uma iphushela kurejista (I-OpenShift ibeka isithombe ekubhaliseni kwayo kwangaphakathi phakathi nesigaba sokwakha). Futhi yilokhu okuzovela esikrinini lapho senza isibonelo sethu, lapho, ngendlela, senze imisebenzi yemigomo hhayi eyodwa ngesikhathi, kodwa ngesikhathi esisodwa:
~/work/repos/eclipse-jkube-demo-project : $ mvn oc:build oc:resource oc:apply
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< meetup:random-generator >-----------------------
[INFO] Building random-generator 0.0.1
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- openshift-maven-plugin:1.0.0-rc-1:build (default-cli) @ random-generator ---
[INFO] oc: Using OpenShift build with strategy S2I
[INFO] oc: Running in OpenShift mode
[INFO] oc: Running generator spring-boot
[INFO] oc: spring-boot: Using Docker image quay.io/jkube/jkube-java-binary-s2i:0.0.7 as base / builder
[INFO] oc: [random-generator:0.0.1] "spring-boot": Created docker source tar /home/rohaan/work/repos/eclipse-jkube-demo-project/target/docker/random-generator/0.0.1/tmp/docker-build.tar
[INFO] oc: Adding to Secret pullsecret-jkube
[INFO] oc: Using Secret pullsecret-jkube
[INFO] oc: Creating BuildServiceConfig random-generator-s2i for Source build
[INFO] oc: Creating ImageStream random-generator
[INFO] oc: Starting Build random-generator-s2i
[INFO] oc: Waiting for build random-generator-s2i-1 to complete...
[INFO] oc: Caching blobs under "/var/cache/blobs".
[INFO] oc: Getting image source signatures
[INFO] oc: Copying blob sha256:cf0f3ebe9f536c782ab3835049cfbd9a663761ded9370791ef6ea3965c823aad
[INFO] oc: Copying blob sha256:57de4da701b511cba33bbdc424757f7f3b408bea741ca714ace265da9b59191a
[INFO] oc: Copying blob sha256:f320f94d91a064281f5127d5f49954b481062c7d56cce3b09910e471cf849050
[INFO] oc: Copying config sha256:52d6788fcfdd39595264d34a3959464a5dabc1d4ef0ae188802b20fc2d6a857b
[INFO] oc: Writing manifest to image destination
[INFO] oc: Storing signatures
[INFO] oc: Generating dockerfile with builder image quay.io/jkube/jkube-java-binary-s2i:0.0.7
[INFO] oc: STEP 1: FROM quay.io/jkube/jkube-java-binary-s2i:0.0.7
[INFO] oc: STEP 2: LABEL "io.openshift.build.source-location"="/tmp/build/inputs" "io.openshift.build.image"="quay.io/jkube/jkube-java-binary-s2i:0.0.7"
[INFO] oc: STEP 3: ENV JAVA_APP_DIR="/deployments" OPENSHIFT_BUILD_NAME="random-generator-s2i-1" OPENSHIFT_BUILD_NAMESPACE="default"
[INFO] oc: STEP 4: USER root
[INFO] oc: STEP 5: COPY upload/src /tmp/src
[INFO] oc: STEP 6: RUN chown -R 1000:0 /tmp/src
[INFO] oc: STEP 7: USER 1000
[INFO] oc: STEP 8: RUN /usr/local/s2i/assemble
[INFO] oc: INFO S2I source build with plain binaries detected
[INFO] oc: INFO S2I binary build from fabric8-maven-plugin detected
[INFO] oc: INFO Copying binaries from /tmp/src/deployments to /deployments ...
[INFO] oc: random-generator-0.0.1.jar
[INFO] oc: INFO Copying deployments from deployments to /deployments...
[INFO] oc: '/tmp/src/deployments/random-generator-0.0.1.jar' -> '/deployments/random-generator-0.0.1.jar'
[INFO] oc: STEP 9: CMD /usr/local/s2i/run
[INFO] oc: STEP 10: COMMIT temp.builder.openshift.io/default/random-generator-s2i-1:48795e41
[INFO] oc: time="2020-08-10T06:37:49Z" level=info msg="Image operating system mismatch: image uses "", expecting "linux""
[INFO] oc: time="2020-08-10T06:37:49Z" level=info msg="Image architecture mismatch: image uses "", expecting "amd64""
[INFO] oc: Getting image source signatures
[INFO] oc: Copying blob sha256:d8e1f35641acb80b562f70cf49911341dfbe8c86f4d522b18efbf3732aa74223
[INFO] oc: Copying blob sha256:b6f081e4b2b6de8be4b1dec132043d14c121e968384dd624fb69c2c07b482edb
[INFO] oc: Copying blob sha256:b7139ad07aa8ce4ed5a132f7c5cc9f1de0f5099b5e155027a23d57f7fbe78b16
[INFO] oc: Copying blob sha256:98972fc90a1108315cc5b05b2c691a0849a149727a7b81e76bc847ac2c6d9714
[INFO] oc: Copying config sha256:27aaadaf28e24856a66db962b88118b8222b61d79163dceeeed869f7289bc230
[INFO] oc: Writing manifest to image destination
[INFO] oc: Storing signatures
[INFO] oc: --> 27aaadaf28e
[INFO] oc: 27aaadaf28e24856a66db962b88118b8222b61d79163dceeeed869f7289bc230
[INFO] oc: Getting image source signatures
[INFO] oc:
[INFO] oc: Pushing image image-registry.openshift-image-registry.svc:5000/default/random-generator:0.0.1 ...
[INFO] oc: Copying blob sha256:f320f94d91a064281f5127d5f49954b481062c7d56cce3b09910e471cf849050
[INFO] oc: Copying blob sha256:cf0f3ebe9f536c782ab3835049cfbd9a663761ded9370791ef6ea3965c823aad
[INFO] oc: Copying blob sha256:57de4da701b511cba33bbdc424757f7f3b408bea741ca714ace265da9b59191a
[INFO] oc: Copying blob sha256:98972fc90a1108315cc5b05b2c691a0849a149727a7b81e76bc847ac2c6d9714
[INFO] oc: Copying config sha256:27aaadaf28e24856a66db962b88118b8222b61d79163dceeeed869f7289bc230
[INFO] oc: Writing manifest to image destination
[INFO] oc: Storing signatures
[INFO] oc: Successfully pushed image-registry.openshift-image-registry.svc:5000/default/random-generator@sha256:aa9e1a380c04ef9174ba56459c13d44420ebe653ebf32884d60fe4306b17306d
[INFO] oc: Push successful
[INFO] oc: Build random-generator-s2i-1 in status Complete
[INFO] oc: Found tag on ImageStream random-generator tag: sha256:aa9e1a380c04ef9174ba56459c13d44420ebe653ebf32884d60fe4306b17306d
[INFO] oc: ImageStream random-generator written to /home/rohaan/work/repos/eclipse-jkube-demo-project/target/random-generator-is.yml
[INFO]
[INFO] --- openshift-maven-plugin:1.0.0-rc-1:resource (default-cli) @ random-generator ---
[INFO] oc: Using docker image name of namespace: default
[INFO] oc: Running generator spring-boot
[INFO] oc: spring-boot: Using Docker image quay.io/jkube/jkube-java-binary-s2i:0.0.7 as base / builder
[INFO] oc: jkube-controller: Adding a default DeploymentConfig
[INFO] oc: jkube-service: Adding a default service 'random-generator' with ports [8080]
[INFO] oc: jkube-healthcheck-spring-boot: Adding readiness probe on port 8080, path='/actuator/health', scheme='HTTP', with initial delay 10 seconds
[INFO] oc: jkube-healthcheck-spring-boot: Adding liveness probe on port 8080, path='/actuator/health', scheme='HTTP', with initial delay 180 seconds
[INFO] oc: jkube-revision-history: Adding revision history limit to 2
[INFO]
[INFO] --- openshift-maven-plugin:1.0.0-rc-1:apply (default-cli) @ random-generator ---
[INFO] oc: Using OpenShift at https://api.crc.testing:6443/ in namespace default with manifest /home/rohaan/work/repos/eclipse-jkube-demo-project/target/classes/META-INF/jkube/openshift.yml
[INFO] oc: OpenShift platform detected
[INFO] oc: Using project: default
[INFO] oc: Creating a Service from openshift.yml namespace default name random-generator
[INFO] oc: Created Service: target/jkube/applyJson/default/service-random-generator.json
[INFO] oc: Creating a DeploymentConfig from openshift.yml namespace default name random-generator
[INFO] oc: Created DeploymentConfig: target/jkube/applyJson/default/deploymentconfig-random-generator.json
[INFO] oc: Creating Route default:random-generator host: null
[INFO] oc: HINT: Use the command `oc get pods -w` to watch your pods start up
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:07 min
[INFO] Finished at: 2020-08-10T12:08:00+05:30
[INFO] ------------------------------------------------------------------------
~/work/repos/eclipse-jkube-demo-project : $ oc get pods -w
NAME READY STATUS RESTARTS AGE
random-generator-1-deploy 1/1 Running 0 14s
random-generator-1-vnrm9 0/1 Running 0 11s
random-generator-s2i-1-build 0/1 Completed 0 1m
random-generator-1-vnrm9 1/1 Running 0 24s
random-generator-1-deploy 0/1 Completed 0 28s
~/work/repos/eclipse-jkube-demo-project : $ oc get routes
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
random-generator random-generator-default.apps-crc.testing random-generator 8080 None
~/work/repos/eclipse-jkube-demo-project : $ curl random-generator-default.apps-crc.testing/random
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 45 0 45 0 0 1666 0 --:--:-- --:--:-- --:--:-- 1730
{
"id": "d80052d9-2f92-43cb-b9eb-d7cffb879798"
}
~/work/repos/eclipse-jkube-demo-project : $
Isifundo sevidiyo
Ukuze ufunde kabanzi mayelana nendlela yokwenza ukuthuthukiswa kwe-Kubernetes kube lula nge-Eclipse JKube, bukela lesi sifundo sevidiyo sokuthi ungalukhipha kanjani ngokushesha uhlelo lokusebenza olulula lwe-Spring Boot ku-Minikube:
isiphetho
Kulesi sihloko, sibonise ukuthi i-Eclipse JKube yenza kanjani impilo ibe lula kunjiniyela we-Java lapho esebenza noKubernetes. Ulwazi olwengeziwe nge-Eclipse JKube lungatholakala ku- futhi kuqhubeke .
Source: www.habr.com