Nick Young
Nick Young
I think it makes sense in general, but will need careful writing of the spec - we can't add the new field as required, but what value should be used...
We currently have a maximum items set of 16 in the validation for rules across all the rule types, so I think we're managing the larger routes concern to some...
Right now, there's #2128 to add some clarify to Policy Attachment's discoverability, but I agree that this would be nice to address soon. #2128 is also going to have a...
Okay, reviewing this, I think I've answered all the outstanding things, it seems that this is ready to move to Implementable, so I'll remove the hold and wait for an...
Hi @tahvane1, I'd recommend reviewing https://docs.cilium.io/en/stable/network/servicemesh/gateway-api/gateway-api/#cilium-s-ingress-config-and-ciliumnetworkpolicy and the example at https://docs.cilium.io/en/stable/network/servicemesh/ingress-and-network-policy/#gs-ingress-and-network-policy to learn more about targeting Network Policy at the `reserved:ingress` identity. In particular, the example of allowing Ingress traffic...
The Network Policy you supplied looks like it should allow traffic for the `reserved:ingress` identity, but remember that if you have a deny-all policy, you'll also need to allow traffic...
TCP and UDP listeners are not currently supported in Cilium, as they require the TCPRoute and UDPRoute objects, which are also not yet supported. You can follow #21929 for the...
We specifically designed Gateways to limit the number of Listeners to encourage people to have smaller numbers of Listeners in each Gateway, and we decided not to have TLS config...
It seems very reasonable to me to ensure that all the valid redirect codes can be used in this enum. But it does raise the question of whether we should...