Hi Mursel, >> Optimal Environment for Production:... "Cluster Manager" itself not mandatory to run 24x7 actually and it's performance doesn't reflect Production Gluu Cluster. It's just a tool to setup and periodic monitor your Gluu Server cluster. >> Currently, we have installed the cluster manager on WSL in a Windows server. Is this a good setup, or is there a better way to host the cluster manager? We are not a great fan of Windows and as far as I remember we don't _officially_ support Cluster Manager in Windows platform. From experience... any DEB/RPM distribution has been a great choice. >> Web App Availability:... It's not mandatory as I mentioned earlier. >> will there be issues if it goes offline, particularly concerning the "key rotation" functionality of the cluster manager? This is a good question, it didn't came into my mind. I'll ask around. >> Health Check Endpoint: ... Cluster Manager itself does it's monitoring but it's only exposed to Cluster Manager [GUI](https://gluu.org/docs/cm/4.4/deploy/#monitoring) However, Gluu Server's own health check endpoints are available which you can use. [Here](https://gluu.org/docs/gluu-server/4.5/operation/health-check/) are they.

Hi Mohib, I appreciate it. I'll wait for your feedback about the CM availability for the key rotation. For example, the cluster managers availability is not required for LDAP replication because these configurations are stored on the Gluu servers. However, for the "key rotation" functionality, I noticed in the LDAP logs of the cluster manager that it modifies the LDAP oxAuth keys (public keys) at regular intervals.

Yes, you are correct. Just confirmed with Cluster Manager team... we need to run CM running if we use Key rotation feature there.

Okay I understand. We will put the CM in a Ubuntu environment so the CM is always available for the key rotation. Thanks for the clarification.

Sounds good, thanks!