Duela 25 urte, Java programazioaren korronte nagusian sartu zen eta, azkenean, aplikazio pilak eraikitzeko oinarrizko elementuetako bat bihurtu zen. Gaur egun, ordea, urte askotan Javari leialak izan diren pertsona eta erakunde asko buru-belarri ari dira migratzen edo plataformara migratzea pentsatzen. edo bere eratorriak esaterako edo .
Zoritxarrez, Kubernetes-ek ikasketa-kurba handia du eta Java programatzaileak ohituta dauden garapen-prozesuan beste geruza operatibo bat sartzen du. Gaur nola erabili esango dizugu , Kubernetesekin eta edukiontziekin lotutako eragiketa gehigarri hauek sinplifikatzeko eta hodeiko plataformarako minik gabeko migrazioa bermatzeko, Java ekosistema ezaguna mantenduz. Gainera, OpenShift plataforman Java aplikazioak nola zabaldu OpenShift Maven plugina erabiliz erakutsiko dugu.
Java garapen-prozesu tradizionala
Garapen-prozesu tradizionala (1. irudia) garatzaileak kodea idaztea dakar, ondoren JAR edo WAR fitxategi moduan inplementazio-unitateak sortzea eta, ondoren, fitxategi horiek web- edo aplikazio-zerbitzari batean zabaldu eta exekutatzea. Horretarako modu nagusia Maven komando-lerrotik erabiltzea edo IntelliJ edo Eclipse bezalako IDE bat erabiltzea da aplikazioak kodetzeko eta paketatzeko. Garatzaileak ohituta daude kodea aldaketak egitera eta dena ondo probatzera kodea konprometitu eta bertsio-kontrolera bidali aurretik.
Arroza. 1. Java garapen-prozesu tradizionala.
Hodeirako Java Garapen Prozesua
Hodeiko aplikazioetara mugitzean, Kubernetes eta . Hori dela eta, orain garatzaileak Java aplikazioak paketatu behar ditu eta irudi horiek deskribatzen dituzten Kubernetes manifestuak sortu. Manifestu hauek Kubernetes exekutatzen duen produkzio-zerbitzariari aplikatzen zaizkio. Era berean, Kubernetes-ek irudi horiek erregistrotik hartzen ditu eta manifestuetan idatzi ditugun konfigurazioen arabera zabaltzen ditu aplikazioak, normalean YAML fitxategiak izan ohi direnak.
Hodeirako trantsizioan Java garapen-prozesu tradizionalaren metamorfosia agertzen da irudian. 2.
Arroza. 2. Hodeirako Java garapen prozesua.
Eclipse JKube
Kubernetesera migratzeak beste geruza operatibo bat gehitzen dio garapen-prozesuari, eta garatzaile asko urduri daude, beren lan nagusian —aplikazio-logikan— bideratu nahi dutelako haiek nola zabaldu beharrean. Eta hor sartzen da jokoan. , garatzaileek beren liburutegiak eta pluginak erabiltzeko aukera ematen diena ( elkarrekin edo ) edukiontziarekin eta Kubernetesekin lotutako eragiketak erraz egiteko, irudiko diagrama jarraituz. 2.
Artikulu honen gainerakoan, Kubernetes ingurunean Java garapen-prozesua nola erraztu erakutsiko dizugu Eclipse JKube Kubernetes Maven Plugin-ekin erabiliz.
Hodeia garatzeko prozesua Eclipse JKube erabiliz
Ikus dezagun 2. irudiko hodeirako Java garapen-eskema apur bat aldatuta, Eclipse JKube eta Kubernetes Maven Plugin-a bertan sartuz, irudian erakusten den moduan. 3.
Arroza. 3. Hodeirako Java garapen-prozesua Eclipse JKube erabiliz.
Ikus dezakegunez, hemen Kubernetes eta edukiontziekin elkarreragiteko eragiketa guztiak (diagraman gorriz nabarmenduta) Eclipse JKube helburu-zeregin lehenetsiekin ordezkatzen dira, Taulan zerrendatuta daudenak. 1.
Taula 1. Eclipse JKube zeregin lehenetsiak.
Task
Etapa
Description
PRE_INTEGRATION_TEST
Docker irudiak eraikitzea
Instalatu
Docker irudiak erregistrora kargatzea
PROCESS_RESOURCES
K8s manifestuak sortzea
BILDU
Sortutako manifestuak K8-ei aplikatzea
DESPLEATU
k8s:apply eta k8s:deploy erabiliz zabaldu ziren K8s baliabideak kentzea
Oharra: Ez baduzu nahi atazek ustezko lehenetsi hauek erabiltzea, eskuz konfigura dezakezu Eclipse JKube zuk zeuk, konfigurazioa onartzen baitu. и .
Orain ikus ditzagun Eclipse JKube eta Kubernetes Maven Plugin erabiltzeko adibideak aplikazioekin lan egiten duzunean.
Kubernetes-en Java aplikazio bat zabaltzea Eclipse JKube erabiliz
Adibide honetan Java aplikazio sinple bat zabalduko dugu cluster batean Eclipse JKube erabiliz. Kubernetes Maven Plugin-a erabiliz, inplementazio-parametroak ezar ditzakegu inolako konfiguraziorik idatzi beharrik gabe.
Erabiltzen dugun aplikazio adibide gisa , JSON irteera sortzen duena /ausazko amaieran:
~/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. urratsa. Deskargatu Kubernetes Maven Plugin
Kubernetes Maven Plugin biltegian dago . Eclipse JKube erabiltzeko Kubernetes Maven Plugin-a gehitu behar duzu zure pom.xml-ra menpekotasun gisa:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>kubernetes-maven-plugin</artifactId>
<version>${jkube.version}</version>
</plugin>
Kubernetes hutsaren ordez OpenShift erabiltzen bada, pom.xml honela aldatzen da:
<plugin>
<groupId>org.eclipse.jkube</groupId>
<artifactId>openshift-maven-plugin</artifactId>
<version>${jkube.version}</version>
</plugin>
2. urratsa. Eraiki docker irudia
Aplikazioaren JAR fitxategia mvn package komandoarekin eraiki daiteke, eta, ondoren, mvn goal zeregina k8s:build aplikazioaren docker irudi bat eraikitzeko erabil daiteke. Kontuan izan irudiaren izena lehenetsia gainidatzi dugula propietate honekin:
<jkube.generator.name>docker.io/rohankanojia/random-generator:${project.version}</jkube.generator.name>
Irudia eraiki aurretik, ziurtatu behar duzu docker deabrua behar bezala azaltzen dela. Hau komando honekin egin daiteke:
$ eval $(minikube docker-env)
Ondoren, mvn k8s:build komandoa sartzen dugu, eta hau da pantailan ikusiko duguna Eclipse JKube eraikitze-ataza erabiliz docker irudia eraikitzean:
~/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 : $
3. urratsa. Kargatu irudia docker erregistrora
Docker irudia eraiki ondoren push erregistroa konfiguratuta (gure kasuan docker.io da), irudi hau erregistrora bidali dezakegu. Hau da Eclipse JKube-ri mvn k8s:push push zeregina egiteko eskatu ondoren bistaratuko dena:
~/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 : $
Irudia bidali ondoren, erregistroan sartuta dagoela egiaztatu behar duzu. Gure kasuan, Docker Hub-en ikusten dugu, irudian ikusten den moduan. 4.
Arroza. 4. Erregistrora bidalitako irudia Docker Hub-en agertu zen.
4. urratsa. Sortu aplikaziorako Kubernetes baliabideen manifestuak
Beraz, aplikazioaren irudia bildu dugu, orain Kubernetesen manifestuak idatzi behar ditugu. Horretarako, Eclipse JKube-k azpiko Java esparruan oinarritutako baliabideen manifestu zurrunak sortzen dituen zeregin bat du (, , Vert.x edo beste batzuk). Manifestua ere pertsonaliza dezakezu XML konfigurazio fitxategi bat erabiliz eta zati gordinak (beharrezko baliabideen manifestuaren zatiak) src/main/jkube aplikazioaren karpetan jarriz. Kasu honetan, zure konfigurazioa sortutako manifestuetara igoko da.
Gure adibidean, dena bere horretan uzten dugu, eta, beraz, Eclipse JKube-k manifestu bat sortzen du lehenetsitako inplementaziorako eta ClusterIP motako zerbitzurako. Eta orduan bakarrik aldatuko dugu zerbitzuaren manifestua zerbitzu mota NodePort-era aldatzeko. Portaera lehenetsia baliogabe dezakezu propietate hau erabiliz:
<jkube.enricher.jkube-service.type>NodePort</jkube.enricher.jkube-service.type>
Hau da pantailako irteerak Eclipse JKube-ri mvn k8s:resource resource zeregina egiteko eskatu ondoren.
~/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. urratsa. Inplementatu aplikazioa Kubernetes klusterean
Orain prest gaude aplikazioa zabaltzeko: bere irudia sortu dugu eta, ondoren, baliabideen manifestuak automatikoki sortu ditugu. Orain hori guztia Kubernetes klusterrean aplikatzea besterik ez da geratzen. Aplikazioa zabaltzeko, kubectl apply -f komandoa erabil dezakezu, noski, baina pluginak guretzat egin dezake. Hau da pantailan agertuko dena Eclipse JKube-ri eskatu ondoren mvn k8s:apply apply zeregina exekutatzeko:
~/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. urratsa. Desplegatu aplikazioak Kubernetes klusterretik
Horretarako, desplegatze-ataza erabiltzen da, aurreko urratsean aplikatu ziren baliabide guztiak kentzen dituena, hau da, aplikatzeko ataza exekutatzen denean. Hau da pantailan ikusiko duguna Eclipse JKube-ri mvn k8s:undeploy undeploy zeregina egiteko eskatu ondoren:
~/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 : $
Zer gehiago egin dezakezu Eclipse JKube-rekin
Beraz, Eclipse JKube eta Kubernetes Maven Plugin-en helburu nagusien zereginak aztertu ditugu, Kubernetes plataformarako Java aplikazioen garapena errazten dutenak. Zeregin hauek teklatutik etengabe sartu nahi ez badituzu, pluginaren konfigurazioan idatz ditzakezu, adibidez, honela:
<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>
Esan beharra dago artikulu honetan ez ditugula kontuan hartu Eclipse JKube eta Kubernetes Maven Plugin-en dauden helburu-zeregin guztiak, beraz, 2. taulan zuretzat ere erabilgarriak izan daitezkeen zeregin gehigarrien zerrenda eskaintzen dugu.
Taula 2. Eclipse JKube helburuko zeregin osagarriak.
Task
Etapa
Description
BALIOZTU
Kubernetes-en exekutatzen ari den aplikazio batetik erregistroak jasotzea.
PACKAGE
Ireki arazketa-ataka bat Kubernetes-en exekutatzen ari den aplikazioa IDEtik zuzenean arazteko.
Instalatu
Instalatu atazarako fork bat sortzea eta sortutako manifestuak Kubernetes klusterrean aplikatzea aplikatzeko zereginaren kasuan bezala.
PACKAGE
Aplikazio baten hedapen bero automatikoa bere izen-espazioaren jarraipena eginez.
Red Hat OpenShift-en Java aplikazioak zabaltzea OpenShift Maven Plugin-a erabiliz
Red Hat OpenShift plataforman gure adibideko aplikazioa zabaltzeko, plugina erabiltzen dugu . Desberdintasun bakarra zereginaren aurrizkia k8s-tik oc-era aldatuko dela izango da. Lehenespenez Kubernetes Maven pluginak egiten du -assemblyak eta OpenShift Maven plugina - asanbladak . Ez dugu aldaketarik egiten gure proiektuan jkube.generator.name propietatea kentzeaz gain, ez baita beharrezkoa erregistrora bultzatzean (OpenShift-ek irudia bere barne-erregistroan jartzen du eraikuntza-fasean). Eta hau da gure adibidea exekutatzen dugunean pantailan agertuko dena, non, bide batez, helburu-zereginak ez banan-banan, aldi berean egiten ditugun:
~/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 : $
Bideo ikasgaia
Eclipse JKube-rekin Kubernetesen garapena erraztu nola erraztu jakiteko, ikusi bideo-tutorial hau Spring Boot aplikazio sinple bat nola azkar zabaldu Minikube-n:
Ondorioa
Artikulu honetan, Eclipse JKube-k Java garatzaile bati bizitza errazten dion Kubernetesekin lan egiten duenean erakutsi dugu. Eclipse JKube-ri buruzko informazio gehiago helbidean aurki daiteke eta abar .
Iturria: www.habr.com