Jeff Mesnil

the operator is not able to deploy application images provisioned with wildfly-maven-plugin

3

Application images created by the `wildfly-maven-plugin`'s `package` goal use *managed* deployments. The deployment bits are stored in the server `data` directory (in the `content` subdir) and the digest of the...

Deploy application built with wildfly-maven-plugin This fixes #249 Signed-off-by: Jeff Mesnil

in `main`, the logs are output in development mode at https://github.com/wildfly/wildfly-operator/blob/76a511db331242488a2f07e93d8829d4e60a76f0/main.go#L77. This is a change from the previous versions and we should revert to production mode by default (by removing...

As an user, I want to pull my application image from a private container registry

1

When the statefulset is created, the container image must be pullable from the container platform. Public images can be pulled without any issue. On OpenShift, any image in the OpenShift...

With #27, the `WildFlyServerSpec` CRD expects the presence of `applicationSource` XOR `applicationImage` field. I've not been able to find a way to express this mutual exclusion of fields with the...

Scaling down is failing with WildFly 18 S2I

9

# Steps to reproduce * use the branch https://github.com/jmesnil/wildfly-operator/tree/105_wildfly_18_S2I that uses S2I for WildFly 18. * run a local operator: `make run-local-operator` * deploy an app built from WildFly 18...

Currently, we have 1 builder image per JDK version. If we want to provide additional JDK version (eg for non-LTS releases such as JDK 19), we have to add a...

[S2I v2] Backwards compatibility with existing S2I images

1

I'm working on updating the Helm Charts for WildFly to work with the new S2I v2 images. As much as possible, I want to avoid breaking backwards compatibility of the...

I'm using WildFly builder image with S2I to generate a Dockerfile and then use `docker` to build the artifacts image. By default, it works: ``` $ s2i --loglevel=10 build https://github.com/wildfly/quickstart.git...

All exceptions and logs (> INFO) must be i18ned