RockteMQ-AI commented on issue #218:
URL:
https://github.com/apache/rocketmq-operator/issues/218#issuecomment-5207330358
**Issue Evaluation**
Category: | Status: **Needs Info**
I verified the codebase. The operator **does** set the environment variable
in the broker container (via fieldRef in ), and the default broker image
entrypoint script writes into .
So the mechanism exists, but it generates a **properties-format** config (),
not XML.
To help diagnose why is not taking effect in your environment, could you
clarify:
1. **Which broker image are you using?** The default alpine image runs
which writes to . If you are using a custom image, this script may not be
executed.
2. **Is your broker reading from XML or properties?** You mentioned RocketMQ
4.9.4 — if the broker is configured to load an XML config file (e.g., ), the
in would not be picked up.
3. **Can you into the broker pod and check the generated config?**
This will show whether is present in the generated config.
If the generated does contain but the broker still binds to the wrong
address, the issue may be in how the broker startup command references the
config file.
---
*Automated evaluation by github-manager*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
