Closed maurice-freitag closed 1 year ago
Hey @maurice-freitag , IMO it's an issue with K8s is populating this env variable automatically, and OPAL uses it unintentionally.
Let me check this more deeply and i'll create a PR for this. Thanks for reporting this 👍
@RazcoDev FYI changing the name of the installed chart to myopal works as well (helm install myopal opal/opal
) 🤠
Makes sense, K8s is creating this env variable using the deployment/service name.
In this case it's opal
, and our "confi" settings using the environment variables with OPAL_
prefix.
Thanks !
Fixed by https://github.com/permitio/opal/pull/442 You don't have to rename your chart :)
I tried installing the chart (0.0.11) with
helm install opal opal/opal
after adding and updating the repo. The installed chart is version 0.0.11:The server never starts properly:
Logs:
For some reason the application code attempts to parse 'tcp://10.43.243.243:7002' to an int and crashes understandibly. A workaround is to set server.extraEnv.OPAL_SERVER_PORT manually, either via
helm install opal opal/opal --set server.extraEnv.OPAL_SERVER_PORT=7002
or a values.yaml file. The server then starts normally.