Well, while it might be a good solution, it feels that a one that will fit non-k8s deployment, and without 54 hosts limitation is also due for wide masses.

While I'm not sure how it would look like, but it somehow feels that some RPC might be leveraged and do self-reporting/discovery how nova/cinder/neutron does with their agents/services. But unfortunately I don't have time right now to work on that in any way, but contributing to such solution is in a backlog at very least...

With that said it also feels that k8s based deployment might be simpler to have their own operator/chart for send evac command rather then rely on another service.... But dunno, not an expert in this specific area.

On Fri, Jan 26, 2024, 10:25 Sam Su (苏正伟) <suzhengwei@inspur.com> wrote:

It sounds like a good potential solution. Would you draft one spec?

发件人: dogyun kim <dogyun7949@gmail.com>
发送时间: 2024年1月26日 15:43
收件人: openstack-discuss@lists.openstack.org
主题: [masakari][masakari-monitors] Feature to monitor hosts by kubernetes

Hi team masakari!

I'm using openstack on kubernetes and also masakari for HA.
I have developed a function monitoring by using kubernetes api internally to masakari-monitors for k8s-native openstack and want to contribute.

blueprint link : https://blueprints.launchpad.net/masakari/+spec/host-monitors-by-kubernetes