Slideee commented on issue #131: URL: https://github.com/apache/rocketmq-operator/issues/131#issuecomment-1261721713
> @Slideee IMO it's quite a good idea, could you provide your design with more details? My advice: > > * `HttpDomainSite` should be kept simple. > * Users can also provide their own domain site service, in that case, the user-predefined one should be preffered. > > And the current way to support updating nameserver addresses is as follows: In RocketMQ 4.9.4 LTS or 5.x, there's a scheduled task to check and update nameserver addresses from `BrokerConfig`, which is updated by `nameservice_controller` if the addresses of nameserver pod are changed. I checked the code of version 4.9.4 and found that there is indeed a new scheduled task to update NamesrvAddr. For `HttpDomainSite` resource, current thinking is as follows: 1. It is based on `Nginx` base image. 2. When the Operator is Reconciled, pod and headless service are created. 3. Run a script to update NamesrvAddr regularly through `ReadinessProbe` under the container. and then NamesrvAddr will exist in the directory inside the pod. 4. Set the `HttpDomainSite` headless service domain name and sub path to the Broker environment variable `ROCKETMQ_NAMESRV_DOMAIN` and `ROCKETMQ_NAMESRV_DOMAIN_SUBGROUP`. However, it is now supported to dynamically update the NamesrvAddr, and it is not clear when the `HttpDomainSite` service is necessary. -- 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]
