chore(ingress): renmae use_native_ingress to use_ingress

Author: duanhongyi

charts/workflow/values.yaml

@@ -49,15 +49,15 @@ global:
   # - gcr: Use Google's GCR
   registry_location: "on-cluster"
   # The host port to which registry proxy binds to
-  host_port: 5555
+  registry_service_port: 5555
   # Prefix for the imagepull secret created when using private registry
   secret_prefix: "private-registry"
   # Experimental feature to use Kubernetes ingress instead of Workflow's drycc-router.
   #
   # Valid values are:
   # - true: drycc-router will not be deployed. Workflow will not be usable until a Kubernetes ingress controller is installed.
   # - false: drycc-router will be deployed (default).
-  use_native_ingress: false
+  use_ingress: false
   # If the Kubernetes cluster uses CNI
   # use_cni: true
   # Set the `listen` variable for registry-proxy's NGINX

…nstalling-workflow/use-native-ingress.md src/installing-workflow/use-ingress.mdsrc/installing-workflow/use-native-ingress.md renamed to src/installing-workflow/use-ingress.md src/installing-workflow/use-native-ingress.md renamed to src/installing-workflow/use-ingress.md

@@ -5,7 +5,7 @@
 Now that Helm is installed and the repository has been added, install Workflow with a native ingress by running:
 
 ```
-$ helm install drycc/workflow --namespace drycc --set global.use_native_ingress=true,controller.platform_domain=drycc.cc
+$ helm install drycc/workflow --namespace drycc --set global.use_ingress=true,controller.platform_domain=drycc.cc
 ```
 
 Where `controller.platform_domain` is a **required** parameter that is traditionally not required for Workflow that is explained in the next section. In this example we are using `drycc.cc` for `$hostname`.
@@ -45,7 +45,7 @@ drycc-workflow-manager-68nu6   1/1       Running   0          5m
 
 ## Install a Kubernetes Ingress Controller
 
-Now that Workflow has been deployed with the `global.use_native_ingress` flag set to `true`, we will need a Kubernetes ingress controller in place to begin routing traffic.
+Now that Workflow has been deployed with the `global.use_ingress` flag set to `true`, we will need a Kubernetes ingress controller in place to begin routing traffic.
 
 Here is an example of how to use [traefik](https://traefik.io/) as an ingress controller for Workflow. Of course, you are welcome to use any controller you wish.