hotelReservation issue - not all pods are running

[stekas7]

Dear all,

I am trying to deploy and do some workload tests on the hotelReservation app on my Kubernetes cluster. I followed the instructions in GitHub, but even after some time not all pods are running. I am attaching a screenshot from the logs of the non-running pods. It seems like some file is missing. I have not edited any file I just downloaded the files and applied them with Kubectl apply -Rf.

Kind Regards

[Feelas]

Not a maintainer, but it reminds me of this comment #320 (comment).

[stekas7]

Not sure about it. I will give it a try to modify the compose file.

[Feelas]

@stekas7 the point is that copying/mounting the config.json should sort out the "Got error while reading config" message and also at the same time "mongodb://" points to an incorrect URI which would be read from config.json if it wasn't missing.

[stekas7]

I tried it today, adding:
configs: server_config: file: ./config.json name: config.json
to the docker-compose file and then running Kubectl apply -Rf, but I still get the exact same error

[Feelas]

The link I mentioned specifically modifying the Dockerfile to inject config.json inside.

I think that the docker-compose file doesn't get applied onto the K8s cluster, you would have to inject (e.g. thru a configMap volume + volumeMounts) the config.json into proper place.

Looks like that would be the hotelReservation/kubernetes/reccomend/recommendation-deployment.yaml which you have to expand.

[stekas7]

Anyone from the DeathStarBench team that could fix this issue?

[stekas7]

So, I am trying to mount the config.json using a configmap I created named hotelrescm. Problem is, I cannot find the correct mount path for the volume mount. Anyone can help? @Feelas maybe you have already solved this?

[Feelas]

@stekas7 try to mount it like here.

So that would be

        - mountPath: config.json
          subPath: config.json
          name: config-json

I guess it should be put exactly in same catalog as "./recommendation" from connect.

[stekas7]

@Feelas Thank you for the response, what do you mean with "I guess it should be put exactly in same catalog as "./recommendation" from connect." Do you mean something in the recommendation-deployment.yaml? I am just editing this file and then applying.

[Feelas]

@stekas7 I meant that probably config.json goes in the same directory as "recommendation" binary (which "command" field in deployment referes to).