You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
support REGISTER_ONLY and ALLOW_ANY mode of egress gateway.
Add result of connection failed in accesslog. Let the user know if it's a normal failure due to authz or an abnormal failure.
Why is this needed:
"Network perimeter security" is a key concern for any enterprise operations team. Network outbound traffic also needs to be secured.
But Kmesh doesn't do anything about outbound traffic right now. While there is no handling of this in ambient mesh either, the handling of outbound traffic is controlled in istio sidecar mode using REGISTER_ONLY and ALLOW_ANY.
Once the outbound traffic has been controlled, we need to add the reason for the connection failure in the accesslog. So that the user knows whether the link failed because of an expected or unexpected result.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
REGISTER_ONLY
andALLOW_ANY
mode of egress gateway.Why is this needed:
"Network perimeter security" is a key concern for any enterprise operations team. Network outbound traffic also needs to be secured.
But Kmesh doesn't do anything about outbound traffic right now. While there is no handling of this in ambient mesh either, the handling of outbound traffic is controlled in istio sidecar mode using
REGISTER_ONLY
andALLOW_ANY
.Once the outbound traffic has been controlled, we need to add the reason for the connection failure in the accesslog. So that the user knows whether the link failed because of an expected or unexpected result.
The text was updated successfully, but these errors were encountered: