openstack
/
kuryr-kubernetes
Code Issues Proposed changes

Merge "Fix spelling errors."

This commit is contained in:
Zuul 2020-12-02 16:26:32 +00:00 committed by Gerrit Code Review
parent f345588f76 643468ae68
commit 1eeb45e634
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/devref/network_policy.rst
View File

@ -173,7 +173,7 @@ Use cases examples
~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~
This section describes some scenarios with a Network Policy being enforced, This section describes some scenarios with a Network Policy being enforced,
what Kuryr componenets gets triggered and what resources are created. what Kuryr components gets triggered and what resources are created.
Deny all incoming traffic Deny all incoming traffic

2
doc/source/devref/port_manager.rst
View File

@ -24,7 +24,7 @@ capturing the design decision currently taken by the kuryr team.
The main purpose of the Port Manager is to perform Neutron resources handling, The main purpose of the Port Manager is to perform Neutron resources handling,
i.e., ports creation and deletion. The main idea behind is to try to minimize i.e., ports creation and deletion. The main idea behind is to try to minimize
the amount of calls to Neutron by ensuring port reusal as well as performing the amount of calls to Neutron by ensuring port reuse as well as performing
bulk actions, e.g., creating/deleting several ports within the same Neutron bulk actions, e.g., creating/deleting several ports within the same Neutron
call. call.

4
doc/source/devref/vif_handler_drivers_design.rst
View File

@ -27,7 +27,7 @@ Kuryr-Kubernetes Controller.
VIF-Handler VIF-Handler
----------- -----------
VIV-handler was intended to handle VIFs. Currently it is responsible for VIF-handler was intended to handle VIFs. Currently it is responsible for
reacting on Pod object events, and for creating/deleting corresponding reacting on Pod object events, and for creating/deleting corresponding
KuryrPort CRD object. KuryrPort CRD object.
@ -146,7 +146,7 @@ Specific ports support
---------------------- ----------------------
Specific ports support is enabled by default and will be a part of the drivers Specific ports support is enabled by default and will be a part of the drivers
to implement it. It is possile to have manually precreated specific ports in to implement it. It is possible to have manually precreated specific ports in
neutron and specify them in pod annotations as preferably used. This means that neutron and specify them in pod annotations as preferably used. This means that
drivers will use specific ports if it is specified in pod annotations, drivers will use specific ports if it is specified in pod annotations,
otherwise it will create new ports by default. It is important that specific otherwise it will create new ports by default. It is important that specific

2
doc/source/specs/pike/contrail_support.rst
View File

@ -34,7 +34,7 @@ hosted VM workloads in Contrail SDN environments
Use Case 2: Allow Kubernetes workloads to leverage advanced OpenContrail based Use Case 2: Allow Kubernetes workloads to leverage advanced OpenContrail based
networking networking
Use Case 3: Enable Kuberentes to create virtual networks via Contrail Use Case 3: Enable Kubernetes to create virtual networks via Contrail
Proposed Change Proposed Change
=============== ===============