This channel is for discussions related to Eclipse JKube, successor of Fabric8 Maven Plugin.
- command:
- chmod
- "777"
- XXX
image: busybox
imagePullPolicy: IfNotPresent
name: jkube-volume-permission
resources:
limits:
cpu: 500m
memory: 2000Mi
requests:
cpu: 250m
memory: 700Mi
cpuLimit, memoryLimit, cpuRequest, memoryRequest to configuration?
<enricher> there should be <includes> and <excludes> list elements where we can specify which enrichers we want to include/exclude
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.
I think it should be possible to support. If we add skipPush configuration field in https://github.com/eclipse/jkube/blob/master/jkube-kit/config/image/src/main/java/org/eclipse/jkube/kit/config/image/ImageConfiguration.java
and then use image configurations filtered based on skipPush=false in PushMojo here: https://github.com/eclipse/jkube/blob/master/kubernetes-maven-plugin/plugin/src/main/java/org/eclipse/jkube/maven/plugin/mojo/build/PushMojo.java#L59
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.
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: IfNotPresentand it is preventing the main container from being started. Anyone knows how can I prevent initcontainers from being generated?
<configuration>
<enricher>
<excludes>
<exclude>jkube-volume-permission</exclude>
</excludes>
</enricher>
<configuration>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?
