Conversation
078f2a1 to
49d7832
Compare
|
/test |
|
This pull request has been automatically marked as stale because it |
|
currently working on the conflicts |
|
This pull request has been automatically marked as stale because it |
49d7832 to
0d31d38
Compare
|
reworked code based on #27464 which simplifies the code in a huge way |
c9e30c7 to
9a4af8c
Compare
|
I think this also fixes #19121 right? |
yeah it does 😊 |
0a8ce70 to
ecb791a
Compare
|
/test |
ecb791a to
659ae7b
Compare
|
/test |
be21684 to
b07f887
Compare
|
rebased from latest main |
|
/test |
There was a problem hiding this comment.
LGTM. I think the main questions I would have are:
- How should we document this new policy construct? Typically we may add some examples under
examplesdirectory and reference them inDocumentation/security/policy/language.rst, presumably also with the optional flags. - How should we regression test that the functionality here works?
|
|
Sounds good to me. Given the Slack discussion I think we agreed on a small change to the user-facing flag, so after resolving that issue and getting CI to pass I think this should be good to merge. |
Head branch was pushed to by a user without write access
b07f887 to
8d44dec
Compare
|
/test |
|
Commit bb6219a does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
|
/test |
3 similar comments
|
/test |
|
/test |
|
/test |
This commit adds a new flag `--enable-node-selector-labels` which takes advantage of the new IdentityScopeRemoteNode. If this flag is enabled it will filter out node labels based on `--node-labels` list and will append that to remote-node label. This also adds a new label source LabelSourceNode="node" which is prepended to all node labels. Signed-off-by: Ondrej Blazek <ondrej.blazek@firma.seznam.cz>
When node-selector labels are enabled this means that entity 'remote-node' still works but now each node also has custom identity based on its labels (including reserved:remote-node). This mean user has now more fine grained control over what kind of remote-node is allowed/blocked. Signed-off-by: Ondrej Blazek <ondrej.blazek@firma.seznam.cz>
|
/test |
1 similar comment
|
/test |
|
/ci-e2e |
|
/ci-ginkgo |
|
/ci-ipsec-upgrade |
This is revival of #22208, based on latest main.
Please take a look at CFP for more details.
When one enables
policy-cidr-match-mode=nodesit allows nodes to be selected by CIDR network policies which is great, but hides the fact that each node in the end has a unique identity fromIdentityScopeRemoteNode.In cases where we have a big clustermesh this results in a lot of identities to be used. Instead we could use this new feature to allow nodes to be selectable by their labels. Which might be filtered out by
--node-labelslist.The code also adds a new label source
LabelSourceNode="node"which addsnode:prefix to node labels.With that one could specify this new
fromNodes/toNodesin their CNPs and allow access only from/to specific nodes:instead of
or
where one would need to define all node IPs and keep track of them perhaps in a
CiliumCIDRGroupresource.Fixes: #21615
Fixes: #19121