fixed typo in next-gen-route docs

F5Networks · Jul 10, 2023 · 4bab102 · 4bab102
1 parent bdcad24
commit 4bab102
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/config_examples/next-gen-routes/README.md b/docs/config_examples/next-gen-routes/README.md
@@ -26,7 +26,7 @@ NextGen Controller uses extendedConfigMap for extending the native resources (ro
 
 ###RouteGroup
 All the routes are grouped by namespaces or namespace-labels into RouteGroups.
-Each RouteGroup shares the same vsAddress, vsName, bigIpPartition and policy CR which is specified in extendedConfigMap
+Each RouteGroup shares the same vserverAddr, vserverName, bigIpPartition and policy CR which is specified in extendedConfigMap
 
 All the routes in the namespace/namespaceLabel are treated as part of one routegroup in this implementation
 
@@ -195,8 +195,8 @@ Base route configuration can be defined in Global ConfigMap. This cannot be over
 | policyCR           | Optional | Name of Policy CR to attach profiles/policies defined in it.            | -                                                      | Local and Global ConfigMap |
 | httpServerPolicyCR | Optional | Name of Policy CR to attach profiles/policies defined in it to HTTP VS. | -                                                      | Local and Global ConfigMap |
 | namespace          | Mandatory | namespace to group the routes                                           | -                                                      | Local and Global ConfigMap |
-| vsAddress          | Mandatory | BigIP Virtual Server IP Address                                         | -                                                      | Local and Global ConfigMap |
-| vsName             | Optional | Name of BigIP Virtual Server                                            | auto                                                   | Local and Global ConfigMap |
+| vserverAddr          | Mandatory | BigIP Virtual Server IP Address                                         | -                                                      | Local and Global ConfigMap |
+| vserverName             | Optional | Name of BigIP Virtual Server                                            | auto                                                   | Local and Global ConfigMap |
 
   **Note**: 1. namespaceLabel is mutually exclusive with namespace parameter.
             2. --namespace-label parameter has to be defined in CIS deployment to use the namespaceLabel in extended ConfigMap.

diff --git a/docs/config_examples/next-gen-routes/migration-guide.md b/docs/config_examples/next-gen-routes/migration-guide.md
@@ -14,7 +14,7 @@
 
 
 ## Overview
-NextGenRoute Controller uses extendedConfigMap for extending the native resources (routes). All the routes are group by namespaces or namespace-labels into RouteGroups. Each RouteGroup shares the same vsAddress, vsName and policy CR  which is specified in extendedConfigMap. 
+NextGenRoute Controller uses extendedConfigMap for extending the native resources (routes). All the routes are group by namespaces or namespace-labels into RouteGroups. Each RouteGroup shares the same vserverAddr, vserverName and policy CR  which is specified in extendedConfigMap. 
 In order to migrate to nextGen we first need to create an extended ConfigMap and policy CR then modify the CIS deployment accordingly. Refer [NextGen Route Documentation](https://github.com/F5Networks/k8s-bigip-ctlr/tree/master/docs/config_examples/next-gen-routes) for more details
 
 ## Migration using defaultRouteGroup