Kabir Khan
Kabir Khan
I believe the initContainers needs to be associated with the wildfly entry in the Helm chart. So (without much research) I believe it can't be moved
That might be possible by using `deploy.initcontainers` https://github.com/wildfly/wildfly-charts/blob/main/charts/wildfly/README.md
@kstekovi @emmartins I added the initContainer stuff since without it (if you make sure you don't have any of the images locally in the kubernetes registry) I can reproduce the...
@emmartins Not sure. It looks like the todo-backend image (which IIRC is WIldFly) is not starting. Too me that seems like it can't connect to postgresql. Maybe the initContainer isn't...
Hi, I've finally been able to try it, and the main issue is that thepostgresql pod isn't starting. Likely the jump from 13.1.5 to 16.2.2 of the bitnami Helm chart...
It garbled my diffs, the two commits can be found here https://github.com/wildfly/quickstart/compare/main...kabir:quickstart:kstekovi-WFLY-19898-fresh?expand=1
@kstekovi @emmartins I have added my commit switching to busybox, and force pushed the branch for this PR (I have admin rights so I am able to do so)
@istudens I see a failure in the new test case https://ci.wildfly.org/buildConfiguration/WF_PullRequest_GalleonLinuxJdk11/366184?expandBuildProblemsSection=true&hideProblemsFromDependencies=false&expandBuildTestsSection=true&hideTestsFromDependencies=false&expandBuildChangesSection=true
Putting this on hold, so @jasondlee, who should be more familiar, can take a look
@jasondlee yes please :-)