Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 06:42
    codecov[bot] commented #680
  • 06:42
    rohanKanojia review_requested #680
  • 06:41
    rohanKanojia commented #680
  • 05:53
    manusa commented #1501
  • 05:52
    manusa commented #1501
  • 05:52
    manusa commented #1501
  • 05:48
    manusa commented #680
  • 05:48
    manusa commented #680
  • 05:48
    manusa commented #680
  • 05:47
    manusa commented #1501
  • 05:45
    manusa commented #1501
  • 05:45
    manusa commented #1501
  • 05:45
    manusa commented #1501
  • 05:42
    manusa commented #1501
  • 05:42
    manusa commented #1501
  • 05:41
    manusa commented #1501
  • 05:39
    manusa commented #1501
  • 05:38
    manusa commented #1501
  • 05:37
    manusa commented #680
  • 05:37
    manusa commented #1501
javastl
@javastl
If I replace <from>openjdk:11</from> with <from>ubuntu:20.04</from> it will replace FROM openjdk:11 with FROM ubuntu:20.04. The pods will not start since the java jre is not present
You are correct that I am using XML in the maven pom.xml for zero configuration. <build>. ....<image>
javastl
@javastl
Can I add the java JRE in another area of the XML assembly rather than in the <FROM></FROM line?
Christian-dev-ops
@Christian-dev-ops
hello guys, how to can use Jkube for maven when i need to add resources limits to jkube-volume-permission? Example:
initContainers:
  - command:
    - chmod
    - "777"
    - XXX
    image: busybox
    imagePullPolicy: IfNotPresent
    name: jkube-volume-permission
    resources:
      limits:
        cpu: 500m
        memory: 2000Mi
      requests:
        cpu: 250m
        memory: 700Mi
Do you think it's a good idea to add additional fieldslike cpuLimit, memoryLimit, cpuRequest, memoryRequest to configuration?
javastl
@javastl
Do you think it's a good idea to add additional fieldslike cpuLimit, memoryLimit, cpuRequest, memoryRequest to configuration? YES. This has be done for the QoS of the pods. Resources are limited and it should be allowed to be configured
Rohan Kumar
@rohanKanojia
okay, Would anyone like to create an issue for this?
Christian-dev-ops
@Christian-dev-ops
okk, I'm going to create an issue. Thanks @rohanKanojia
Another question, is possible to disable jkube-volume-permission enricher?
Rohan Kumar
@rohanKanojia
I think it's possible
In <enricher> there should be <includes> and <excludes> list elements where we can specify which enrichers we want to include/exclude
robinroos
@robinroos
Same question, but other direction. Does jkube have base images for Java 8 ??
Rohan Kumar
@rohanKanojia
Umm, from what I remember when we switched from Fabric8 Images to JKube images, we made JDK11 as base. If you're looking for JDK8, maybe you can try out Fabric8 JDK8 image we used in Fabric8 Maven Plugin: https://hub.docker.com/r/fabric8/java-centos-openjdk8-jdk/ . I think it should work okay
Marc Nuri
@manusa
The JDK11 image should be compatible with your Java 8 binaries? What's your usecase?
As Rohan points out, any of the older images should be good for you.
But as I said, I'm very curious, especially now that we want to bump the base image to JDK 17
robinroos
@robinroos
Two separate projects. The first targets Java 17 very soon. The second is still on Java 8 and faces upgrade challenges. But I will probably force the issue and take it to a more recent Java edition before looking to containerise it.
Marc Nuri
@manusa
What I mean is if there's any trouble running that JDK8 compiled project in the JDK11->17 image?
Jave is meant to be backwards compatible always (though we know that's not always true ;) )
Attyuttam
@Attyuttam
I have a remote session started using "mvn k8s:debug -Pkubernetes". But I am not sure how to enable remote debugging session on VS Code. Is it necessary to use Eclipse or IntelliJ only ? This is in regards to the issue #966
Rohan Kumar
@rohanKanojia
Umm, I haven't used VSCode. I'm not sure how to configure it. Does this help? https://stackoverflow.com/questions/44372595/how-do-attach-to-a-remote-java-debugger-using-visual-studio-code
Attyuttam
@Attyuttam
Thanks @rohanKanojia . Let me try this out
Rohan Kumar
@rohanKanojia
:+1:
Diom
@Diom

Hey, wondering if anyone has any input on this issue? eclipse/jkube#1195

Essentially I am looking for a way to safely skip building and pushing a subset of the images that I have configured in my POM. It skips the build but not the push, causing the build to fail. I can only see the skipPush options which skips all pushes.

Rohan Kumar
@rohanKanojia
Hello
Matt Pavlovich
@mattrpav
For interacting w/ AWS EKS.. is having to constantly re-gen tokens still the best practice?
We have some operators, etc.. we need to be free of any cli
Marc Nuri
@manusa
I think this question is better suited for the Fabric8 Kubernetes Client channel (https://gitter.im/fabric8io/kubernetes-client)
I see in your project that you are still on a very early version of the Fabric8 client. We added automatic token refresh capabilities in the latest releases of the client. I think your case might already be covered OOTB.
hussamalmotlak
@hussamalmotlak

Good Morning, I have a small question. I am using Jkube to deploy configuration and create a pod on openshift. This Pod uses a PersistentVolumClaim, which I mount to the directory: /run/app/logs
In the DeploymentConfigs, this is being autogenerated by Jkube:

initContainers:
        - name: jkube-volume-permission
          image: busybox
          command:
            - chmod
            - '777'
            - /run/app/logs
          resources: {}
          volumeMounts:
            - name: logs-storage
              mountPath: /run/app/logs
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: IfNotPresent

and it is preventing the main container from being started. Anyone knows how can I prevent initcontainers from being generated?

hussamalmotlak
@hussamalmotlak
I think the problem is just the jkube-volume-permission, so how can I pause it using maven?
Marc Nuri
@manusa
you can exclude the enricher
trying to find an example
<configuration>
  <enricher>
    <excludes>
      <exclude>jkube-volume-permission</exclude>
    </excludes>
  </enricher>
<configuration>
hussamalmotlak
@hussamalmotlak
Thank you Marc, I will try that
Matt Pavlovich
@mattrpav
@manusa thanks for the pointers, i'll check into that.
Marc Nuri
@manusa
Starting release process for Eclipse JKube 1.6.0
Rohan Kumar
@rohanKanojia
:+1:
Rohan Kumar
@rohanKanojia
Thanks a lot!
robinroos
@robinroos
Congratulations on the release of 1.6.0 !

I have noticed on difference. In the expression for image name

<jkube.generator.name>nexus3.uk.mizuho-sc.com:25665/%g/%a:%l</jkube.generator.name>
previously the %g token expanded to the OpenShift project name, but now it expands to the trailing token in the maven group name. The new behaviour seems more consistent with the k8s docs. Is the change documented at all on the JKube side?

Also, is there an alternative token which would expand to the OpenShift project name?
Marc Nuri
@manusa
Maybe related to eclipse/jkube#910 ?
But this was already changed in 1.5.0
Hrushikesh
@Hrushi20

Hey I get this error while running the command mvn clean install k8s:build k8s:resource k8s:apply

 NAME                         READY   STATUS         RESTARTS   AGE
helloworld-6d7f67847-szjh6   0/1     ErrImagePull   0          4m32s

I am not sure how to fix this issue.
Thank You

Hrushikesh
@Hrushi20
Also a small doubt regarding the command mvn k8s:build. When I run the command mvn k8s:build, is the entire project being build and running or are we downloading org.eclipse.jkube:jkube from the maven repository and running the code.