docs: network policy: remove SCTP from missing features list
#35238
Conversation
The `policy enforcement` bullet in the referenced issue (cilium#5719) is completed. Looks like the network policy support was added with cilium#20033. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
|
/test |
|
The referenced issue isn't completed, and SCTP support is broken if there's a k8s service in front (since we can't generate SCTP hashes => can't rewrite addresses / perform NAT). Should we revert this change? |
What's missing for |
|
I see what you're saying. SCTP can be not fully implemented but as long as the policy primitive is supported then this note should not exist in the docs under network policy. I was thinking from an end-to-end perspective that if someone connects to a Kubernetes service over SCTP, then network policy will not allow the traffic. The underlying cause is not the policy engine but it's because we don't support services with SCTP. The end result is that SCTP may not fully work. But perhaps if that's the nuance we're going for, it should be mentioned as a limitation somewhere else in the docs rather than in the network policy section. 👍 makes sense to me. No need to take action on this PR. |
The
policy enforcementbullet in the referenced issue (#5719) is completed. Looks like the network policy support was added with #20033.