25 yil oldin Java dasturlashning asosiy oqimiga kirdi va oxir-oqibat dastur steklari quriladigan asosiy elementlardan biriga aylandi. Biroq, bugungi kunda ko'p yillar davomida Java-ga sodiq bo'lgan ko'plab odamlar va tashkilotlar platformaga ko'chib o'tish yoki ko'chirish bilan band. yoki uning hosilalari, masalan yoki .
Afsuski, Kubernetes keskin o'rganish egri chizig'iga ega va Java dasturchilari o'rganib qolgan rivojlanish jarayoniga yana bir operatsion qatlamni kiritadi. Bugun biz sizga qanday foydalanishni aytib beramiz , Kubernetes va konteynerlar bilan bog'liq ushbu qo'shimcha operatsiyalarni soddalashtirish va tanish Java ekotizimini saqlab, bulutli platformaga og'riqsiz o'tishni ta'minlash. Bundan tashqari, biz OpenShift Maven plaginidan foydalangan holda Java ilovalarini OpenShift platformasida qanday joylashtirishni ko'rsatamiz.
An'anaviy Java ishlab chiqish jarayoni
An'anaviy rivojlanish jarayoni (1-rasm) ishlab chiquvchi kod yozishni, so'ngra JAR yoki WAR fayllari ko'rinishida joylashtirish birliklarini yaratishni va keyin bu fayllarni veb yoki dastur serverida joylashtirish va ishga tushirishni o'z ichiga oladi. Buni amalga oshirishning asosiy usuli Maven-dan buyruq satridan foydalanish yoki ilovalarni kodlash va paketlash uchun IntelliJ yoki Eclipse kabi IDE-dan foydalanishdir. Ishlab chiquvchilar kodni o'zgartirish va kodni topshirishdan va versiyani boshqarishga topshirishdan oldin hamma narsani sinchkovlik bilan sinab ko'rishga odatlangan.
Guruch. 1. An'anaviy Java ishlab chiqish jarayoni.
Bulut uchun Java ishlab chiqish jarayoni
Bulutli ilovalarga o'tishda Kubernetes va . Shuning uchun, endi ishlab chiquvchi Java dasturlarini paketlashi kerak va ushbu tasvirlarni tavsiflovchi Kubernetes manifestlarini yarating. Keyinchalik bu manifestlar Kubernetes ishlaydigan ishlab chiqarish serveriga qo'llaniladi. O'z navbatida, Kubernetes bu rasmlarni registrdan oladi va biz odatda YAML fayllari bo'lgan manifestlarda yozgan konfiguratsiyalarga muvofiq ilovalarni joylashtiradi.
Bulutga o'tishda Java-ning an'anaviy rivojlanish jarayonining metamorfozi rasmda ko'rsatilgan. 2.
Guruch. 2. Bulut uchun Java ishlab chiqish jarayoni.
Eclipse JKube
Kubernetes-ga o'tish rivojlanish jarayoniga yana bir operatsion qatlam qo'shadi va ko'plab ishlab chiquvchilar bundan asabiylashadi, chunki ular ularni qanday joylashtirishdan ko'ra o'zlarining asosiy ishlariga - dastur mantig'iga e'tibor berishni xohlashadi. Va bu erda u o'ynaydi. , bu ishlab chiquvchilarga o'z kutubxonalari va plaginlaridan foydalanishga imkon beradi ( bilan birga yoki ) shakldagi diagrammaga rioya qilib, konteyner va Kubernetes bilan bog'liq operatsiyalarni osonlikcha bajarish. 2.
Ushbu maqolaning qolgan qismida biz sizga Eclipse JKube-dan Kubernetes Maven plaginidan foydalangan holda Kubernetes muhitida Java ishlab chiqish jarayonini qanday soddalashtirishni ko'rsatamiz.
Eclipse JKube yordamida bulutli ishlab chiqish jarayoni
Keling, rasmda ko'rsatilganidek, Eclipse JKube va Kubernetes Maven plaginini kiritgan holda, 2-rasmdagi bulut uchun biroz o'zgartirilgan Java ishlab chiqish sxemasini ko'rib chiqaylik. 3.
Guruch. 3. Eclipse JKube yordamida bulut uchun Java ishlab chiqish jarayoni.
Ko'rib turganimizdek, bu erda Kubernetes va konteynerlar bilan o'zaro ishlash bo'yicha barcha operatsiyalar (diagrammada qizil rang bilan belgilangan) jadvalda keltirilgan standart Eclipse JKube maqsad vazifalari bilan almashtiriladi. 1.
Jadval 1. Eclipse JKube standart vazifalari.
Maqsad
Stage
tavsifi
PRE_INTEGRATION_TEST
Docker tasvirlarini yaratish
INSTALL
Docker tasvirlarini ro'yxatga olish kitobiga yuklash
PROCESS_RESOURCES
K8 manifestlarini yaratish
TURMUSH
Yaratilgan manifestlarni K8-larga qo'llash
QO'LLANIB BERISH
k8s:apply va k8s:deploy yordamida joylashtirilgan K8 resurslarini olib tashlash
Eslatma: Vazifalarning ushbu taxminiy standart sozlamalardan foydalanishini xohlamasangiz, Eclipse JKube-ni o'zingiz uchun qo'lda sozlashingiz mumkin, chunki u orqali konfiguratsiyani qo'llab-quvvatlaydi. ΠΈ .
Endi ilovalar bilan ishlashda Eclipse JKube va Kubernetes Maven plaginidan foydalanish misollarini ko'rib chiqamiz.
Eclipse JKube yordamida Kubernetes-da Java ilovasini o'rnatish
Ushbu misolda biz klasterda oddiy Java ilovasini joylashtiramiz Eclipse JKube yordamida. Kubernetes Maven plaginidan foydalanib, biz hech qanday konfiguratsiya yozmasdan joylashtirish parametrlarini o'rnatishimiz mumkin.
Misol sifatida biz foydalanamiz , bu /tasodifiy so'nggi nuqtada JSON chiqishini ishlab chiqaradi:
~/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"
}
1-qadam. Kubernetes Maven plaginini yuklab oling
Kubernetes Maven plagini omborda . Eclipse JKube-dan foydalanish uchun siz Kubernetes Maven plaginini pom.xml-ga bog'liqlik sifatida qo'shishingiz kerak:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>kubernetes-maven-plugin</artifactId>
<version>${jkube.version}</version>
</plugin>
Agar sof Kubernetes o'rniga OpenShift ishlatilsa, pom.xml quyidagicha o'zgartiriladi:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>openshift-maven-plugin</artifactId>
<version>${jkube.version}</version>
</plugin>
2-qadam. Docker tasvirini yarating
Ilovaning JAR faylini mvn paketi buyrug'i bilan qurish mumkin, keyin esa mvn maqsad vazifasi k8s:build ilovaning docker tasvirini yaratish uchun ishlatilishi mumkin. Esda tutingki, biz ushbu xususiyat bilan standart rasm nomini bekor qildik:
<jkube.generator.name>docker.io/rohankanojia/random-generator:${project.version}</jkube.generator.name>
Tasvirni yaratishdan oldin siz docker demonining to'g'ri ta'sirlanganligiga ishonch hosil qilishingiz kerak. Buni quyidagi buyruq yordamida amalga oshirish mumkin:
$ eval $(minikube docker-env)
Keyin biz mvn k8s:build buyrug'ini kiritamiz va Eclipse JKube qurish vazifasi yordamida docker tasvirini yaratishda ekranda buni ko'ramiz:
~/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 : $
Qadam 3. Tasvirni docker registriga yuklang
Push registrini sozlangan holda docker tasvirini yaratganimizdan so'ng (bizning holatlarimizda bu docker.io), biz ushbu rasmni registrga yuborishimiz mumkin. Eclipse JKube-dan mvn k8s: push push vazifasini bajarishni so'raganimizdan so'ng, bu ko'rsatiladi:
~/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 : $
Tasvirni yuborganingizdan so'ng, uning registrga kiritilganligini tekshirishingiz kerak. Bizning holatda, biz buni oddiygina Docker Hub-da ko'ramiz, rasmda ko'rsatilganidek. 4.
Guruch. 4. Ro'yxatga olish kitobiga yuborilgan tasvir Docker Hub'da paydo bo'ldi.
4-qadam. Ilova uchun Kubernetes resurs manifestlarini yarating
Shunday qilib, biz dastur tasvirini yig'dik, endi biz Kubernetes manifestlarini yozishimiz kerak. Buni amalga oshirish uchun Eclipse JKube-da Java asosi asosida qattiq resurs manifestlarini yaratuvchi vazifa mavjud (, , Vert.x yoki boshqa). Shuningdek, siz XML konfiguratsiya faylidan foydalanib va ββsrc/main/jkube ilova papkasida xom fragmentlarni (kerakli resurs manifestining fragmentlari) joylashtirish orqali manifestni sozlashingiz mumkin. Bunday holda, sizning konfiguratsiyangiz yaratilgan manifestlarga yuklanadi.
Bizning misolimizda biz hamma narsani avvalgidek qoldiramiz va shuning uchun Eclipse JKube standart joylashtirish va ClusterIP tipidagi xizmat uchun manifest yaratadi. Va shundan keyingina biz xizmat turini NodePort ga o'zgartirish uchun xizmat manifestini o'zgartiramiz. Siz quyidagi xususiyatdan foydalanib standart xatti-harakatni bekor qilishingiz mumkin:
<jkube.enricher.jkube-service.type>NodePort</jkube.enricher.jkube-service.type>
Eclipse JKube-dan mvn k8s: resurs resurs vazifasini bajarishni so'raganimizdan so'ng, ekran chiqishi shunday ko'rinadi.
~/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 : $
5-qadam. Ilovani Kubernetes klasteriga joylashtiring
Endi biz dasturni ishga tushirishga tayyormiz: biz uning tasvirini yaratdik va keyin avtomatik ravishda resurs manifestlarini yaratdik. Endi bularning barchasini Kubernetes klasteriga qo'llash qoladi. Ilovani joylashtirish uchun, albatta, kubectl apply -f buyrug'idan foydalanishingiz mumkin, ammo plagin buni biz uchun qila oladi. Eclipse JKube-dan mvn k8s:apply application topshirig'ini bajarishni so'raganimizdan so'ng ekranda shunday ko'rinadi:
~/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"
}
6-qadam. Kubernetes klasteridan ilovalarni bekor qiling
Buning uchun undeploy vazifasidan foydalaniladi, bu oddiygina oldingi bosqichda, ya'ni qo'llash vazifasi bajarilganda qo'llanilgan barcha resurslarni olib tashlaydi. Eclipse JKube-dan mvn k8s:undeploy undeploy vazifasini bajarishni so'raganimizdan so'ng ekranda buni ko'ramiz:
~/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 : $
Eclipse JKube bilan yana nima qilishingiz mumkin
Shunday qilib, biz Kubernetes platformasi uchun Java ilovalarini ishlab chiqishni osonlashtiradigan Eclipse JKube va Kubernetes Maven Plugin-ning asosiy maqsadli vazifalarini ko'rib chiqdik. Agar siz ushbu vazifalarni doimiy ravishda klaviaturadan kiritishni xohlamasangiz, ularni plagin konfiguratsiyasiga yozishingiz mumkin, masalan:
<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>
Aytish kerakki, ushbu maqolada biz Eclipse JKube va Kubernetes Maven plaginidagi barcha maqsadli vazifalarni ko'rib chiqmadik, shuning uchun biz 2-jadvalda siz uchun foydali bo'lishi mumkin bo'lgan qo'shimcha vazifalar ro'yxatini taqdim etamiz.
Jadval 2. Qo'shimcha Eclipse JKube maqsad vazifalari.
Maqsad
Stage
tavsifi
TASHLATISH
Kubernetesda ishlayotgan ilovadan jurnallar qabul qilinmoqda.
PACKAGE
Kubernetesda ishlayotgan ilovangizni toΚ»gΚ»ridan-toΚ»gΚ»ri IDEβdan disk raskadrovka qilish uchun disk raskadrovka portini oching.
INSTALL
O'rnatish vazifasi uchun vilka yaratish va yaratilgan manifestlarni Kubernetes klasteriga qo'llash vazifasidagi kabi qo'llash.
PACKAGE
Ilovaning nom maydonini kuzatish orqali avtomatik ravishda ishga tushirish.
OpenShift Maven plaginidan foydalanib, Red Hat OpenShift-da Java ilovalarini o'rnatish
Bizning misolimizdagi dasturni Red Hat OpenShift platformasida joylashtirish uchun biz plagindan foydalanamiz . Farqi shundaki, vazifa prefiksi k8s dan oc ga o'zgaradi. Odatiy bo'lib Kubernetes Maven plagini qiladi -assemblylar va OpenShift Maven plagini - assemblies . Biz jkube.generator.name xususiyatini olib tashlashdan tashqari loyihamizga hech qanday o'zgartirish kiritmayapmiz, chunki bu registrga o'tishda talab qilinmaydi (OpenShift yaratish bosqichida tasvirni ichki registrga joylashtiradi). Aytgancha, biz maqsadli vazifalarni bir vaqtning o'zida emas, balki bir vaqtning o'zida bajargan misolimizni ishga tushirganimizda ekranda shunday bo'ladi:
~/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 : $
Video dars
Eclipse JKube yordamida Kubernetes rivojlanishini qanday osonlashtirish haqida ko'proq ma'lumot olish uchun Minikube-da oddiy Spring Boot ilovasini qanday tezda o'rnatish bo'yicha ushbu video qo'llanmani tomosha qiling:
xulosa
Ushbu maqolada biz Eclipse JKube qanday qilib Kubernetes bilan ishlashda Java dasturchisi hayotini osonlashtirishini ko'rsatdik. Eclipse JKube haqida qo'shimcha ma'lumotni quyidagi manzilda topishingiz mumkin va .
Manba: www.habr.com