openstack/kuryr-kubernetes
Code Issues Proposed changes

updates docs to "kubectl create deployment"

Browse Source 
With the new default Kubernetes 1.18 version used by Kuryr,
the command "kubectl run" does not create a Kubernetes Deployment
anymore, but instead creates a Pod.
The Kuryr docs should get updated to still support a
Deployment creation with the command "kubectl create deployment"

Change-Id: I8df10e64d71cc224e08825987d538693df1719f3
Closes-Bug:  #1897391
This commit is contained in:
Kafilat Adeleke 2020-10-08 07:36:53 -07:00
parent cb65522a00
commit 78488bcf32
7 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contrib/pools-management/README.rst
View File

@ -185,7 +185,7 @@ We can see that now we have 7 subports, 3 of them attached to `trunk0` and 4
After that, if we create a new pod, we can see that the pre-created subports
are being used::
$ kubectl run demo --image=celebdor/kuryr-demo
$ kubectl create deployment demo --image=celebdor/kuryr-demo
$ kubectl scale deploy/demo --replicas=2
$ kubectl get pods
NAME READY STATUS RESTARTS AGE

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

@ -255,7 +255,7 @@ Create the following pod with label ``role=monitoring``:
.. code-block:: console
$ kubectl run monitor --image=busybox --restart=Never --labels=role=monitoring
$ kubectl create deployment monitor --image=busybox --restart=Never --labels=role=monitoring
The generated CRD contains an ingress rule allowing traffic on port 8080 from
the created pod, and an egress rule allowing traffic to everywhere, since no

2
doc/source/installation/devstack/basic.rst
View File

@ -133,7 +133,7 @@ To test kuryr-kubernetes itself try creating a Kubernetes pod:
.. code-block:: console
$ kubectl run --image busybox test -- sleep 3600
$ kubectl create deployment --image busybox test -- sleep 3600
$ kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
test-3202410914-1dp7g 0/1 ContainerCreating 0 7s <none> localhost

4
doc/source/installation/network_namespace.rst
View File

@ -118,10 +118,10 @@ Testing the network per namespace functionality
.. code-block:: console
$ kubectl run -n test1 --image kuryr/demo demo
$ kubectl create deployment -n test1 --image kuryr/demo demo
deployment "demo" created
$ kubectl run -n test2 --image kuryr/demo demo
$ kubectl create deployment -n test2 --image kuryr/demo demo
deployment "demo" created
$ kubectl -n test1 get pod -o wide

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

@ -27,7 +27,7 @@ deployment with:
.. code-block:: console
$ kubectl run demo --image=celebdor/kuryr-demo
$ kubectl create deployment demo --image=celebdor/kuryr-demo
deployment "demo" created
After a few seconds, the container is up an running, and a neutron port was

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

@ -8,7 +8,7 @@ successful:
.. code-block:: console
$ kubectl run demo --image=celebdor/kuryr-demo
$ kubectl create deployment demo --image=celebdor/kuryr-demo
$ kubectl scale deploy/demo --replicas=2
$ kubectl expose deploy/demo --port=80 --target-port=8080

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

@ -10,7 +10,7 @@ We first create a deployment named demo:
.. code-block:: console
$ kubectl run --image=yboaron/kuryr-udp-demo demo
$ kubectl create deployment --image=yboaron/kuryr-udp-demo demo
deployment "demo" created
As the next step, we will scale the deployment to 2 pods: