chore(ingress): change global.use_ingress to ingress.enabled

Author: duanhongyi

charts/workflow/values.yaml

@@ -52,12 +52,6 @@ global:
   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_ingress: false
   # If the Kubernetes cluster uses CNI
   # use_cni: true
   # Set the `listen` variable for registry-proxy's NGINX
@@ -239,6 +233,17 @@ router:
       https: ""
       healthz: ""
 
+ingress:
+  # 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).
+  enabled: false
+  # annotations:
+  #   kubernetes.io/ingress.class: nginx
+  #   kubernetes.io/tls-acme: 'true'
+
 workflow-manager:
   versions_api_url: https://versions.drycc.cc
   doctor_api_url: https://doctor.drycc.cc

src/installing-workflow/use-ingress.md src/installing-workflow/ingress.mdsrc/installing-workflow/use-ingress.md renamed to src/installing-workflow/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_ingress=true,controller.platform_domain=drycc.cc
+$ helm install drycc/workflow --namespace drycc --set ingress.enabled=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_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 `ingress.enable` 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.