chore(workflow): change experimental_native_ingress to use_native_ingress

Author: duanhongyi

charts/workflow/values.yaml

@@ -57,7 +57,7 @@ global:
   # 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).
-  experimental_native_ingress: false
+  use_native_ingress: false
   # If the Kubernetes cluster uses CNI
   # use_cni: true
   # Set the `listen` variable for registry-proxy's NGINX

mkdocs.yml

@@ -37,7 +37,7 @@ nav:
     - Configuring Postgres: installing-workflow/configuring-postgres.md
     - Configuring the Registry: installing-workflow/configuring-registry.md
     - Chart Provenance: installing-workflow/chart-provenance.md
-    - Experimental Native Ingress: installing-workflow/experimental-native-ingress.md
+    - Use Native Ingress: installing-workflow/use-native-ingress.md
   - Users:
     - Command Line Interface: users/cli.md
     - Users and Registration: users/registration.md

src/installing-workflow/index.md

@@ -50,7 +50,7 @@ More rigorous installations would benefit from using outside sources for the fol
 
 #### (Experimental) Kubernetes Native Ingress
 
-Workflow now offers [experimental native ingress](experimental-native-ingress.md) to take advantage of native Kubernetes routing. Any compatible Kubernetes ingress controller can be used in place of Workflow's nginx-based drycc-router. Follow [this guide](experimental-native-ingress.md) to enable experimental native ingress.
+Workflow now offers [experimental native ingress](use-native-ingress.md) to take advantage of native Kubernetes routing. Any compatible Kubernetes ingress controller can be used in place of Workflow's nginx-based drycc-router. Follow [this guide](use-native-ingress.md) to enable experimental native ingress.
 
 ## Add the Drycc Chart Repository
 

…-workflow/experimental-native-ingress.md …nstalling-workflow/use-native-ingress.mdsrc/installing-workflow/experimental-native-ingress.md renamed to src/installing-workflow/use-native-ingress.md src/installing-workflow/experimental-native-ingress.md renamed to src/installing-workflow/use-native-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.experimental_native_ingress=true,controller.platform_domain=drycc.cc
+$ helm install drycc/workflow --namespace drycc --set global.use_native_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.experimental_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_native_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.