openstack/kuryr-kubernetes
Code Issues Proposed changes

Minor fixes on docs

Browse Source 
This commit fixes some minor typos and tweaks on the devref
documentation.

Change-Id: Ib62c05e512440bba95cdcc23481dfd2d3ab98619
This commit is contained in:
Daniel Mellado 2018-02-23 12:27:05 +01:00
parent 5294977098
commit 59f63fb880
No known key found for this signature in database
GPG Key ID: C905561547B09777
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -38,7 +38,7 @@ Controller is a supervisor component responsible to maintain translation of
networking relevant Kubernetes model into the OpenStack (i.e. Neutron) model.
This can be considered as a centralized service (supporting HA mode in the
future).
CNI driver is responsible for binding kubernetess pods on worker nodes into
CNI driver is responsible for binding kubernetes pods on worker nodes into
Neutron ports ensuring requested level of isolation.
Please see below the component view of the integrated system:
@ -66,7 +66,7 @@ Design Principles
Kuryr Controller Design
-----------------------
Controller is responsible for watching Kubernetess API endpoints to make sure
Controller is responsible for watching Kubernetes API endpoints to make sure
that the corresponding model is maintained in Neutron. Controller updates K8s
resources endpoints' annotations to keep neutron details required by the CNI
driver as well as for the model mapping persistency.

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

@ -61,7 +61,7 @@ The following scheme describes OCP-Route controller SW architecture:
:align: center
:width: 100%
Similiar to Kubernetes Ingress, each OCP-Route object being translated to a L7
Similar to Kubernetes Ingress, each OCP-Route object being translated to a L7
policy in L7 router, and the rules on OCP-Route become L7 (URL) mapping rules
in that L7 policy.
The L7 policy is configured to forward the filtered traffic to LbaaS Pool.

2
doc/source/installation/containerized.rst
View File

@ -85,7 +85,7 @@ Below is the list of available variables:
In case of using ports pool functionality, we may want to make the
kuryr-controller not ready until the pools are populated with the existing
ports. To achive this a readiness probe must be added to the kuryr-controller
ports. To achieve this a readiness probe must be added to the kuryr-controller
deployment. To add the readiness probe, in addition to the above environment
variables or the kuryr-controller configuration file, and extra environmental
variable must be set:

2
doc/source/specs/queens/network_policy.rst
View File

@ -310,7 +310,7 @@ Possible optimization:
Kubernetes label-selector divided into 2 types of queries "match-labels",
and "match-expression" [10]_. "match-labels" selects a closed list of labels
while "match-expression" selects all pods that match to paticular expression.
while "match-expression" selects all pods that match to particular expression.
This spec suggests to create a watch for each label-selector query, because in
"match-expression" queries it is not possible to determine if pod matches the