Browse Source

Fix spelling errors.

Corrects typos in kuryr-kubernetes documentation.

Change-Id: Id53f321ef94d2ed1802c28cebefd7040c9944526
Closes-Bug: #1906521
changes/53/765153/1
Tabitha 2 months ago
parent
commit
643468ae68
4 changed files with 5 additions and 5 deletions
  1. +1
    -1
      doc/source/devref/network_policy.rst
  2. +1
    -1
      doc/source/devref/port_manager.rst
  3. +2
    -2
      doc/source/devref/vif_handler_drivers_design.rst
  4. +1
    -1
      doc/source/specs/pike/contrail_support.rst

+ 1
- 1
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,
what Kuryr componenets gets triggered and what resources are created.
what Kuryr components gets triggered and what resources are created.
Deny all incoming traffic


+ 1
- 1
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,
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
call.


+ 2
- 2
doc/source/devref/vif_handler_drivers_design.rst View File

@ -27,7 +27,7 @@ Kuryr-Kubernetes Controller.
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
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
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
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


+ 1
- 1
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
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
===============


Loading…
Cancel
Save