-
Notifications
You must be signed in to change notification settings - Fork 387
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
Update Antrea-native policy doc for Namespace labels #2596
Conversation
Add note regarding how to use the Namespace by Name feature in K8s and Antrea-native network policies depending on the K8s version. Signed-off-by: abhiraut <rauta@vmware.com>
docs/antrea-network-policy.md
Outdated
|
||
### K8s clusters with version 1.21 and above | ||
|
||
Starting with K8s v1.21, all Namespaces will be labeled with `kubernetes.io/metadata.name: <namespaceName>` [label](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/#automatic-labelling) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting with K8s v1.21, all Namespaces will be labeled with `kubernetes.io/metadata.name: <namespaceName>` [label](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/#automatic-labelling) | |
Starting with K8s v1.21, all Namespaces are labeled with the `kubernetes.io/metadata.name: <namespaceName>` [label] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
docs/antrea-network-policy.md
Outdated
### K8s clusters with version 1.21 and above | ||
|
||
Starting with K8s v1.21, all Namespaces will be labeled with `kubernetes.io/metadata.name: <namespaceName>` [label](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/#automatic-labelling) | ||
provided that the `NamespaceDefaultLabelName` feature gate is enabled. K8s NetworkPolicy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should emphasize that the feature gate is enabled by default in v1.21, this was never an alpha feature, it went straight to Beta
in v1.22, it is GA and cannot even be disabled anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Signed-off-by: abhiraut <rauta@vmware.com>
Codecov Report
@@ Coverage Diff @@
## main #2596 +/- ##
===========================================
- Coverage 60.10% 42.18% -17.92%
===========================================
Files 282 153 -129
Lines 22337 18491 -3846
===========================================
- Hits 13426 7801 -5625
- Misses 7491 9986 +2495
+ Partials 1420 704 -716
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/skip-all |
* Update Antrea-native policy doc for Namespace labels Add note regarding how to use the Namespace by Name feature in K8s and Antrea-native network policies depending on the K8s version. Signed-off-by: abhiraut <rauta@vmware.com> * Add note regarding feature gate deletion Signed-off-by: abhiraut <rauta@vmware.com>
Add note regarding how to use the Namespace by Name feature in K8s and Antrea-native network policies depending on the
K8s version.
Signed-off-by: abhiraut rauta@vmware.com