Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 12:44
    codecov[bot] commented #927
  • 12:34
    sonarcloud[bot] commented #927
  • 12:34
    sonarcloud[bot] commented #927
  • 12:32
    manusa labeled #937
  • 12:32
    manusa labeled #937
  • 12:32
    manusa labeled #937
  • 12:32
    manusa opened #937
  • 12:22
    manusa labeled #876
  • 12:22
    manusa labeled #806
  • 12:21
    manusa commented #806
  • 12:20
    manusa labeled #936
  • 12:20
    manusa labeled #936
  • 12:20
    manusa labeled #936
  • 12:20
    manusa opened #936
  • 12:09
    manusa commented #927
  • 12:09
    manusa review_requested #905
  • 12:08
    manusa commented #927
  • 12:06
    manusa commented #927
  • 12:03
    manusa commented #927
  • 11:59
    manusa commented #927
Rohan Kumar
@rohanKanojia
okay.
@kumar-cloud : What issue are you facing?
Slok
@kumar-cloud
I have added the testcase for the changes. Could you please help me to review ..
Marco Ronconi
@m.ronconi_gitlab
hello, I need to set the following annotation (kubernetes.io/ingress.class: "nginx") to Ingress, but the name contains a char "/" and it is not possible to define it via XML enricher. Do you know an alternative?
Thanks.
~
7 replies
Rohan Kumar
@rohanKanojia
You can try placing a small YAML fragment that just contains the annotation part: https://github.com/eclipse/jkube/blob/master/quickstarts/maven/external-resources/src/main/jkube/deployment.yml#L15
Marco Ronconi
@m.ronconi_gitlab
I tried, but if I use the YAML fragment (ingress.yml) with only the specific annotation, the generated YAML file is not enriched with XML definitions.
Rohan Kumar
@rohanKanojia
Hm, I think maybe mixing XML and resource fragment configuration is not supported. Could you please try moving XML definition to fragment?
Marco Ronconi
@m.ronconi_gitlab
If i moving the XML definition in fragment works fine. Thanks a lot.
Rohan Kumar
@rohanKanojia
@m.ronconi_gitlab : Np, Thanks a lot for trying out jkube :-)
Cristiano GaviĆ£o
@cvgaviao

Hi all. I'm researching alternatives for our current docker-daemon based image build. I would like to hear any suggestions from you.
Currently, we are building an image using dockerFile with multi-stages feature.

In the first stage, I take a graal-vm image and I install native-image on it.
In the next stage, I copy our project's generated jars to it and run native-image tool on them.
And in the last stage, I take a small Linux distro and copy the artifacts from stage 2 to it.

Question: can we achieve that using docker-daemon-less feature of jkube ?

Marc Nuri
@manusa
I'm not sure what you're referring to with docker daemon-less feature. I've never tried a mutli-stage build with the Dockerfile mode, but it should work.
2 replies
robinroos
@robinroos
Hi Marc / Rohan. I am trying to push images to our in-house Nexus (Docker Registry) whilst still doing an S2I build in OpenShift. I get the following warning:
[WARNING] oc: Image is pushed to OpenShift's internal registry during oc:build goal. Skipping...
So far I have configured the registry tag withing the plugin configuration to point to our Nexus. Is there something else to do, or am I attempting the impossible? Thanks and regardsm, Robin.
16 replies
Marc Nuri
@manusa
image.png
Noel O'Connor
@noeloc_twitter
Hi, I'm struggling to use jkube on an existing quarkus multimodule project. For some reason jKube cannot detect that it's a quarkus project and then can't generate the correct resources. How does jkube detect that it's a quarkus project ?
Rohan Kumar
@rohanKanojia
oh, could this be related to eclipse/jkube#923
Which version of quarkus are you using?
JKube has this concept of generators in which it creates opinionated container images by checking your plugins: https://github.com/eclipse/jkube/blob/master/jkube-kit/jkube-kit-quarkus/src/main/java/org/eclipse/jkube/quarkus/generator/QuarkusGenerator.java#L69
Noel O'Connor
@noeloc_twitter
thanks Rohan, I'll try that....I do have the plugin but only on the parent pom so that might be the issue
Rohan Kumar
@rohanKanojia
Do you have the project available publicly somewhere so that we can also try out and check?
Noel O'Connor
@noeloc_twitter
yep...hold on 1 min
https://github.com/noelo/istio-demo just a playground at the moment I'm using for a few things
Noel O'Connor
@noeloc_twitter
yep just confirmed it was linked to the jkube#923 that you mentioned
Rohan Kumar
@rohanKanojia
For now you can build jkube 1.5.0-SNAPSHOT locally and get going. This fix should be available in next release
Noel O'Connor
@noeloc_twitter
excellent, thanks for this
Rohan Kumar
@rohanKanojia
Thanks for trying out jkube :-) . Feel free to ask any questions. We would be really happy if jkube works out for your use case.
Noel O'Connor
@noeloc_twitter
another question: is there an example of a maven multi-module project that works with oc:resource
It seems that during oc:resource the generator tries to find the quarkus jar but there isn't on in the parent project
and there doesnt' seem to be a way in which I can say process the modules but ignore the parent
I'm not sure if this is even possible with jkube
Noel O'Connor
@noeloc_twitter
never mind I figure it out...I added the skipResource=true on the parent and false on the modules
Rohan Kumar
@rohanKanojia
:+1:
Marc Nuri
@manusa
Hi Noel, regarding multi-module there are different approaches.
One of them should be to have a final module that collects the resources generated by the rest of the modules in the project.
This module should depend on the rest of the modules. The generated package should contain a YAML artifact with the collection of the rest of resources (jkube-dependency enricher).
One of the fuse examples works this way, I'll try to find a link for you.
Marc Nuri
@manusa
So in your https://github.com/noelo/istio-demo you could have a final module uber-yml;P that would depend on the rest of modules that do generate YAMLs. This module should collect the resources generated by the rest. Here you could add for example the helm goal execution so that a single chart was produced.
Noel O'Connor
@noeloc_twitter
excellent, a single chart was exactly what I was hoping for, I'll try it out but if you find that fuse example I'd appreciate it, it's not in the quickstarts as far as I can see....
Marc Nuri
@manusa
I couldn't find it.
There's an internal issue that has a sample reproducer project
Noel O'Connor
@noeloc_twitter
no worries, you've set me on the right path so I'll try it out anyway...cheers
Marc Nuri
@manusa
:thumbsup:
robinroos
@robinroos
OpenJDK 17 has been released. Once the necessaru UBI is in place do I merely have to set maven.compiler.source and maven.compiler.target to get an OpenJDK 17 image?
Rohan Kumar
@rohanKanojia
I think we need to discuss how we're going to provide jdk17 based images. Maybe what you're suggesting would be our approach. We'll check project's jdk and switch base image based on that. I would appreciate if you could open an issue where we can discuss this.
Marc Nuri
@manusa
The plan is to provide a JDK17 compatible base image once the package is out.
(and we release 1.5)
Rohan Kumar
@rohanKanojia
Someone from Kogito team also pinged me today regarding release of 1.5.0
Marc Nuri
@manusa

If you provide your own, then

maven.compiler.source and maven.compiler.target to get an OpenJDK 17 image?

Yes, that's enough

Rohan Kumar
@rohanKanojia
They were migrating from fabric8-maven-plugin to jkube and bumped into eclipse/jkube#815
Marc Nuri
@manusa
1.5 should be released before the 21st of October
Rohan Kumar
@rohanKanojia
cool, Thanks.
Marc Nuri
@manusa
Our base image can be upgraded before, but won't be part of 1.5. You could use that base image with earlier versions of JKube by overriding: jkube.generator.from