Avoid initContainer while mounting a volume

[thibaut-fluteaux-infy]

Description

Since I switch from fabric8 to JKUBE, When I add a volume in my description.yaml.
An initContainer using busybox is automatically added, was not the case with fabric8.

The main issue, my openshift instance dont have access to busybox image (due to corporate restriction)

Info

• Eclipse JKube version : 1.4.0
• Maven version (mvn -v) : 3.8.1

• Kubernetes / Red Hat OpenShift setup and version : 3.11

[rohanKanojia]

Is this duplicate of #891 ? If yes, you might be able to specify image like this:

<plugin>
    <groupId>org.eclipse.jkube</groupId>
    <artifactId>kubernetes-maven-plugin</artifactId>
    <version>${jkube.version}</version>
    <configuration>
      <enricher>
        <config>
            <jkube-volume-permission>
              <imageName>name-foo</imageName>
            </jkube-volume-permission>
        </config>
      </enricher>
    </configuration>
</plugin>

[thibaut-fluteaux-infy]

Thanks for the help to change the image, is there any option to avoid the usage of init container ?
with Fabric8 it was fully working without initcontainer.
regards,

[rohanKanojia]

@thibaut-fluteaux-infy : Would it be possible for you to share a reproducer project? I will help me debug cause for behavioral difference between two plugins.

[thibaut-fluteaux-infy]

considering volumeclaim "volumetest" allready exist.
here is my reproducer : https://github.com/thibaut-fluteaux-infy/jkube-kmp
maven profile :
-fmp for fabric8
-jkube for jkube

regards

[rohanKanojia]

I see you're using quite an old version of the Fabric8 Maven Plugin. I tried with the latest version of FMP v4.4.1 and I was able to see initContainers generated.

I think this change was done by me in fabric8io/fabric8-maven-plugin#1318

[thibaut-fluteaux-infy]

thanks for your answer, no way to disable the usage of init container by jkube ?

[rohanKanojia]

Right now, no. If you want we can add a configuration option to disable this here:

https://github.com/eclipse/jkube/blob/cce1b0de09a3657ec9000b3097d7266daa49aaec/jkube-kit/enricher/generic/src/main/java/org/eclipse/jkube/enricher/generic/VolumePermissionEnricher.java#L94

However, we need to decide if it's really the way we would like to go.

[kuailexingmao]

I encountered the same problem and did not want to use initContainer automatically loaded in Depl0ymentConfig, so I disabled jkube-volume-Permission.My configuration is as follows:

<configuration>
       <enricher>
          <excludes>
                 jkube-volume-permission
           <excludes>
        </enricher>
</configuration>

[rohanKanojia]

I've moved out functionality unrelated to Volume permissions in #1179

Now in order to avoid initContainer you just need to exclude the enricher as @kuailexingmao suggested.