chore(ingress): renmae use_native_ingress to use_ingress

Author: duanhongyi

charts/builder/templates/builder-deployment.yaml

@@ -46,7 +46,7 @@ spec:
             - name: "DRYCC_REGISTRY_SERVICE_HOST"
               value: "127.0.0.1"
             - name: "DRYCC_REGISTRY_SERVICE_PORT"
-              value: "{{ .Values.global.host_port }}"
+              value: "{{ .Values.global.registry_service_port }}"
             - name: "HEALTH_SERVER_PORT"
               value: "8092"
             - name: "EXTERNAL_PORT"

charts/builder/templates/builder-service.yaml

@@ -11,6 +11,6 @@ spec:
       targetPort: 2223
   selector:
     app: drycc-builder
-{{ if .Values.global.use_native_ingress }}
+{{ if .Values.global.use_ingress }}
   type: "LoadBalancer"
 {{ end }}

charts/builder/values.yaml

@@ -12,6 +12,6 @@ global:
   # Valid values are:
   # - true: The drycc controller will now create Kubernetes ingress rules for each app, and ingress rules will automatically be created for the controller itself.
   # - false: The default mode, and the default behavior of Drycc workflow.
-  use_native_ingress: false
+  use_ingress: false
   # Role-Based Access Control for Kubernetes >= 1.5
   use_rbac: false