Bug 1504090
Summary: | [RFE] Kuryr-kubernetes NetworkPolicy support | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Antoni Segura Puimedon <asegurap> |
Component: | Networking | Assignee: | Luis Tomas Bolivar <ltomasbo> |
Networking sub component: | kuryr | QA Contact: | GenadiC <gcheresh> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | aos-bugs, asegurap, gcheresh, ltomasbo, piqin, racedoro, tsedovic, xtian |
Version: | 4.2.0 | Keywords: | FutureFeature, Triaged |
Target Milestone: | --- | ||
Target Release: | 4.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-kuryr-kubernetes-0.6.2-0.20190305141049.a019712.el8ost | Doc Type: | Release Note |
Doc Text: |
A network policy is a specification of how groups of pods are allowed to communicate with each other and other network endpoints.
Kuryr implements network policies by creating a security group for each policy and several rules into it depending on the network policy spec.
To enable network policies in kuryr, several handlers must be enabled:
- The namespace handler to create a Neutron Network per namespace
- The policy handler that is in charge of acting upon network policy CRUD actions
- The pod_label handler that reacts to changes in pod labels that are referred by NPs
- The kuryrnetpolicy handler that keeps track of kuryr CRDs associated to NPs
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-21 11:15:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1651222 |
Description
Antoni Segura Puimedon
2017-10-19 13:39:25 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:2811 |