)]}'
{"doc/source/devref/kuryr_kubernetes_design.rst":[{"author":{"_account_id":11600,"name":"Michał Dulko","email":"michal.dulko@gmail.com","username":"dulek"},"change_message_id":"ef320c2c4b6b27fc9914963e4f50ed03053e1705","unresolved":false,"context_lines":[{"line_number":59,"context_line":"   security groups assignment profiles."},{"line_number":60,"context_line":"#. The communication of the pod binding data between Controller and CNI driver"},{"line_number":61,"context_line":"   should rely on existing communication channels, currently through the"},{"line_number":62,"context_line":"   KuryrPord CRDs."},{"line_number":63,"context_line":"#. CNI Driver should not depend on Neutron. It gets all required details"},{"line_number":64,"context_line":"   from Kubernetes API server (currently through Kubernetes CRDs),"},{"line_number":65,"context_line":"   therefore depending on Controller to perform its translation tasks."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_6f73ecb5","line":62,"range":{"start_line":62,"start_character":3,"end_line":62,"end_character":12},"updated":"2020-08-28 14:24:16.000000000","message":"KuryrPort","commit_id":"326e7e201d406bfb6a91803524cd4fc269b29381"}],"doc/source/devref/network_policy.rst":[{"author":{"_account_id":11600,"name":"Michał Dulko","email":"michal.dulko@gmail.com","username":"dulek"},"change_message_id":"ef320c2c4b6b27fc9914963e4f50ed03053e1705","unresolved":false,"context_lines":[{"line_number":123,"context_line":"depending on the type of pod event, if the pod is affected by the network"},{"line_number":124,"context_line":"policy and if a new security group rule is needed. Also, it triggers the"},{"line_number":125,"context_line":"translation of the pod rules to the affected service. Note, that KuryrPort"},{"line_number":126,"context_line":"takes over most of the Vif handler functionality, although it has to be enabled"},{"line_number":127,"context_line":"together with Vif handler."},{"line_number":128,"context_line":""},{"line_number":129,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_0f5eb011","line":126,"range":{"start_line":126,"start_character":23,"end_line":126,"end_character":26},"updated":"2020-08-28 14:24:16.000000000","message":"I\u0027d capitalize it as VIF.","commit_id":"326e7e201d406bfb6a91803524cd4fc269b29381"},{"author":{"_account_id":11600,"name":"Michał Dulko","email":"michal.dulko@gmail.com","username":"dulek"},"change_message_id":"ef320c2c4b6b27fc9914963e4f50ed03053e1705","unresolved":false,"context_lines":[{"line_number":124,"context_line":"policy and if a new security group rule is needed. Also, it triggers the"},{"line_number":125,"context_line":"translation of the pod rules to the affected service. Note, that KuryrPort"},{"line_number":126,"context_line":"takes over most of the Vif handler functionality, although it has to be enabled"},{"line_number":127,"context_line":"together with Vif handler."},{"line_number":128,"context_line":""},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"The Namespace handler"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_6f980ccc","line":127,"range":{"start_line":127,"start_character":14,"end_line":127,"end_character":17},"updated":"2020-08-28 14:24:16.000000000","message":"Same.","commit_id":"326e7e201d406bfb6a91803524cd4fc269b29381"}]}