k8s Readme changes (#45)

README.md

@@ -60,4 +60,4 @@ Troubleshoot
 ------------
 
 If you get a message ``` Cloud Network Automation License not available or Infoblox WAPI user not having sufficient permissions.``` in the cni-infoblox-daemon log then you have to check for the 
-"Cloud Network Automation License" has aplied and also check for sufficient permissions for the "Infoblox WAPI User" as given in the prerequisite.
+"Cloud Network Automation License" has applied and also check for sufficient permissions for the "Infoblox WAPI User" as given in the prerequisite.

docs/README-K8S.md

@@ -44,11 +44,8 @@ For example (/etc/cni/net.d/infoblox-ipam.conf):
         "type": "infoblox",
         "subnet": "10.0.0.0/24",
         "gateway": "10.0.0.1",
-        "routes": [
-                {"dst": "0.0.0.0/0"}
-                ],
         "network-view": "cni_view"
-        "prefix-length":"24"
+        
     }
 }
 ```
@@ -58,7 +55,7 @@ It can be done by the command ``ip link set eth0 promisc on`` . The promiscuous
 The following are the IPAM attributes:
 - "type" (Required): specifies the plugin type and is also the file name of the plugin executable.
 - "subnet" (Optional): specifies the CIDR to be used for the network. This is a well-known CNI attribute and is used by the driver.
-- "gateway" (Optional): specifies the gateway for the network. This is a well-known CNI attribute and is simply passed through to CNI.
+- "gateway" (Optional): specifies the gateway for the network. This is a well-known CNI attribute and is simply passed through to CNI, If it is mentioned then the gateway is created else will not create.
 
 - "routes" (Optional): specifies the routes for the network. This is a well-known CNI attribute and is simply passed through to CNI.
 - "network-view" (Optional): specifies the Infoblox network view to use for this network. This is a Infoblox IPAM driver specific attribute.
@@ -209,7 +206,7 @@ When opting for different pod cidrs in each worker node, in that case CNI networ
 - subnet
 - gateway
 
-The name should be different because relevent network will be created in Infoblox applinaces so we can't hava a network with same name and different subnet. The subnet/cidr and gatway are different because in background routes & iptables will be configured in each node for respective subnet/cidr only. 
+The name should be different because relevant network will be created in Infoblox appliances so we can't have a network with same name and different subnet. The subnet/cidr and gateway are different because in background routes & iptables will be configured in each node for respective subnet/cidr only. 
 
 User have to manually update the CNI network conf file. so use this **k8s/cni-infoblox-plugin-without-net-conf.yaml** file to deploy cni-infoblox-plugin daemonset only. It will just copy the **infoblox** plugin binary only to all the worker nodes.
 
@@ -260,7 +257,7 @@ How do we install Infoblox CNI Plugin ?
 ```
     kubectl create -f k8s/cni-infoblox-daemon.yaml
 ```
-cni-infoblox-daemon daemonset should be created before starting the plugin. It requied a docker image which is available at [infoblox/cni-infoblox-daemon](https://hub.docker.com/r/infoblox/cni-infoblox-daemon/) which has the binary in an image of cni-infoblox-daemon.
+cni-infoblox-daemon daemonset should be created before starting the plugin. It required a docker image which is available at [infoblox/cni-infoblox-daemon](https://hub.docker.com/r/infoblox/cni-infoblox-daemon/) which has the binary in an image of cni-infoblox-daemon.
 
 NOTE: Don't forget to update base64 encoded wapi-password in k8s/cni-infoblox-daemon.yaml