This message was deleted.
# harvester
a
This message was deleted.
r
• Is possible to change password-based SSH auth after installation? • Is possible to deploy Havester to an internal dummy network and use some kind of OAUTH/IPALLOWLIST proxy for UI ? • Is possible to setup some kind of VPN for UI before installation?
Did not You try some Crowdsec / fail2ban implementation for Nginx Ingress to at least drop brute force attempts ?
b
This sounds like a network design problem to me. You should not be exposing anything to the internet unless necessary. Use a couple vlans, setup a management network with nat to internet, etc.
I've seen plenty of people directly expose esxi and vcenter to the internet and all end up paying for it later. It's just not necessary or wise. Harvester, rancher, etc in my opinion should be treated the same.