Secure the CR (compute resources) from outside attacks to Agent
If you login to a CR you can see connections incoming to the CR agent. This should by default only be allowed to/from other CRs and management any not require custom firewall rules after configuration.
agent: 2024/02/05 16:17:00 http: TLS handshake error from xx.xx.xx.xx:59618: read tcp xx.xx.xx.xx8080->xx.xx.xx.xx:59618: read: connection reset by peer
1
vote
![](https://secure.gravatar.com/avatar/b18d62533ee545ba6ebc99065c66c290?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)