Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Upgrade Note For Deny Policy Fix #26245

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
36 changes: 36 additions & 0 deletions Documentation/operations/upgrade.rst
Original file line number Diff line number Diff line change
Expand Up @@ -342,6 +342,42 @@ Annotations:
to prevent the possibility of connectivity disruptions. Note: this issue does not
affect setups using a persistent etcd cluster instead of the ephemeral one bundled
with the *clustermesh-apiserver*.
* Deny policies now always take precedence over allow policies. Previously, a CIDR-based
allow policy would always allow traffic, even if there was an overlapping CIDR-based deny policy
to deny the same traffic. Now, a CIDR-based deny policy drops traffic when there is
an allow policy for the same traffic.

Verify that all of your CIDR-based deny and allow policies work
as intended. The following example shows an allow policy that would previously allow
all egress traffic to ``20.1.1.1`` for its selector, but that traffic will now be dropped
by the deny policy:

.. code-block:: yaml

apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
name: "allow-to-external-service"
spec:
endpointSelector:
matchLabels:
app: some-specific-app
egress:
- toCIDR:
- 20.1.1.1/32

.. code-block:: yaml

apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
name: "deny-all-external-egress-traffic"
spec:
endpointSelector: {}
egressDeny:
- toCIDR:
- 0.0.0.0/0


Removed Options
~~~~~~~~~~~~~~~
Expand Down