Jeff Mesnil

> Did you run helm dependency update before installing the chart? No. As I mentioned, if I run it before I install from `target/jkube/helm/kubernetes`, it works. The doc at https://www.eclipse.org/jkube/docs/kubernetes-maven-plugin/#jkube:helm...

@rohanKanojia Indeed, a Helm archive that contains dependencies can not be updated. The issue with the archive generated by JKube is that it does not contain the dependencies specified in...

> ohk, you mean jkube doesn't include the dependent charts. Exactly. So the tgz provided by JKube is not installable if it contains dependencies. I'm not sure how you want...

@rohanKanojia the dependencies are *not* included when you want to package a Helm archive, you have to run `helm dep up` to pull the dependencies. As an example, starting from...

The public header should only declare the prop as readonly (the value changes depending on the connection status so a client must not be able to change it). Could you...

I was able to deploy an application images created by the wildfly-maven-plugin with the following changes: * remove the volume mounted for `data` * add several volumes mounted for the...

#244 contains the changes to be able to deploy application image built with the `wildfly-maven-plugin`. However they break the existing integration tests that relies on previous WildFly S2I images (before...

#244 is not enough to fix the issue reliably. We have many subsystems and extensions that writes to the `data` directory (eg for audit logging, messaging). The operator can not...

This issue was resolved in https://issues.redhat.com/browse/WFMP-185 and the operator is able to deploy application provisioned with the wildfly-maven-plugin as long as the version is 4.1.0.Beta2 or above

This is related to the same feature for the Helm Chart for WildFly https://github.com/wildfly/wildfly-charts/issues/82