Open schmidp opened 3 weeks ago
its fixed by adding:
SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
to configData
I wonder why that is not on per default?
its fixed by adding:
SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
to configData
I wonder why that is not on per default?
@Mortom123 Would it make sense to make this the default?
I would argue that this is a matter of preference.
SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
overwrites springs default configuration file bundled into the .jar.
When coding the manager part of the helm chart, I decided that its easier to use the properties from the repo source tree instead of the one bundled into the container. Hence, one should overwrite all variables as needed from the single configMap that holds all the attributes as environment variables without fiddling around with the files inside the container. Have a look at the docs 1 2
Maybe @schmidp can figure out which key(s) the culprit is and we can add it to the configMap definition.
I also wonder, why this error does not occur in CI/CD?
Might be some missing keys (DRIVER_CLASS_NAME
) in the configData in your values.yml
? The default is:
configData:
REDIRECT_HOST: "http://127.0.0.1"
REDIRECT_PORT: "9527"
LOG_LEVEL: "INFO"
# DB
URL: "jdbc:postgresql://127.0.0.1:5432/pulsar_manager"
DRIVER_CLASS_NAME: "org.postgresql.Driver"
# enables the "message peeking" feature
PULSAR_PEEK_MESSAGE: "true"
Describe the bug I am trying to setup a development pulsar environment in Kubernetes and pulsar-manager does not seem to work out of the box. I see the following log in the postgresql db log:
and in the pulsar-manager.log
To Reproduce
Deploy helm chart with the following config (I use flux):
Expected behavior Pulsar manager starts up and I can login.