This is an automated email from the ASF dual-hosted git repository.

houshengbo pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-openwhisk-deploy-kube.git


The following commit(s) were added to refs/heads/master by this push:
     new f5fbeb4  Simplify instructions for editing the nginx ConfigMap. (#41)
f5fbeb4 is described below

commit f5fbeb4fefd93323b878bb98d5d83daa7fb16f8b
Author: Ben Browning <ben...@gmail.com>
AuthorDate: Wed Jul 26 10:37:53 2017 -0400

    Simplify instructions for editing the nginx ConfigMap. (#41)
    
    `kubectl` has a built-in `edit` command that saves a couple of steps
    compared to using `kubectl get` and `kubectl replace` directly.
    
    I have signed the Apache CLA as "Benjamin M. Browning".
---
 kubernetes/nginx/README.md | 21 ++-------------------
 1 file changed, 2 insertions(+), 19 deletions(-)

diff --git a/kubernetes/nginx/README.md b/kubernetes/nginx/README.md
index 2eecf8f..98402e0 100644
--- a/kubernetes/nginx/README.md
+++ b/kubernetes/nginx/README.md
@@ -51,27 +51,10 @@ kubectl apply -f nginx.yml
 
 ## Update Nginx ConfigMap
 
-When updating the nginx ConfigMap, you will need to have the
-actual yaml file. To obtain the generated YAML file run:
-
-```
-kubectl -n openwhisk get cm nginx -o yaml > nginx_configmap.yml
-```
-
-Then you can manually edit the fields by hand. Please note that you
-will need to remove a couple of fields from the `metadata` section.
-
-```
-  creationTimestamp: 2017-06-21T15:39:56Z
-  resourceVersion: "2156"
-  selfLink: /api/v1/namespaces/openwhisk/configmaps/nginx
-  uid: e0585576-5697-11e7-aef9-080027a9c6c9
-```
-
-When you have finished editing the yaml file, run:
+To update the nginx ConfigMap:
 
 ```
-kubectl replace -f nginx_configmap.yml
+kubectl -n openwhisk edit cm nginx -o yaml
 ```
 
 Kubernetes will then go through an update any deployed Nginx

-- 
To stop receiving notification emails like this one, please contact
['"commits@openwhisk.apache.org" <commits@openwhisk.apache.org>'].

Reply via email to