A database or cache that answers on the public internet is one of the most direct ways data gets stolen. Some of these services ship with no password by default, and automated scanners across the internet look for them constantly. Kubernetes, kubelet and etcd are worse still: reaching them can mean reaching everything they run. These ports are rarely opened on purpose — they are left open by a firewall rule copied from staging, a quick debugging session, or a cloud security group nobody revisited.
Remote-administration ports such as SSH and RDP are a different kind of risk. They are often intentional, but every one of them is a door that attackers will keep trying passwords against. Knowing exactly which are open lets you decide whether each one should be there, restricted to a VPN or specific IPs, or closed.
The value of this check is that it looks from where an attacker looks. Your cloud console shows the rules you meant to write; this shows what actually answers from outside, on the IP addresses your verified hostname resolves to, and on paid plans it is re-checked by the daily monitoring scan, so a port that opens next month does not go unnoticed.