You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> **For Kubernetes deployments**, you can configure the `global.hub` parameter in Helm values to use a mirror registry closer to your region. This applies to both Higress component images and built-in Wasm plugin images:
For other installation methods such as Helm deployment under K8s, please refer to the official [Quick Start documentation](https://higress.io/en-us/docs/user/quickstart).
90
102
91
103
If you are deploying on the cloud, it is recommended to use the [Enterprise Edition](https://www.aliyun.com/product/apigateway?spm=higress-github.topbar.0.0.0)
Copy file name to clipboardExpand all lines: helm/higress/README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,7 +178,7 @@ The command removes all the Kubernetes components associated with the chart and
178
178
| global.enableStatus | bool |`true`| If true, Higress Controller will update the status field of Ingress resources. When migrating from Nginx Ingress, in order to avoid status field of Ingress objects being overwritten, this parameter needs to be set to false, so Higress won't write the entry IP to the status field of the corresponding Ingress object. |
179
179
| global.externalIstiod | bool |`false`| Configure a remote cluster data plane controlled by an external istiod. When set to true, istiod is not deployed locally and only a subset of the other discovery charts are enabled. |
180
180
| global.hostRDSMergeSubset | bool |`false`||
181
-
| global.hub | string |`"higress-registry.cn-hangzhou.cr.aliyuncs.com/higress"`| Default hub for Istio images. Releases are published to docker hub under 'istio' project. Dev builds from prow are on gcr.io|
181
+
| global.hub | string |`"higress-registry.cn-hangzhou.cr.aliyuncs.com"`| Default hub (registry) for Higress images. For Higress deployments, images are pulled from: {hub}/higress/{image} For built-in plugins, images are pulled from: {hub}/{pluginNamespace}/{plugin-name} Change this to use a mirror registry closer to your deployment region for faster image pulls.|
182
182
| global.imagePullPolicy | string |`""`| Specify image pull policy if default behavior isn't desired. Default behavior: latest images will be Always else IfNotPresent. |
183
183
| global.imagePullSecrets | list |`[]`| ImagePullSecrets for all ServiceAccount, list of secrets in the same namespace to use for pulling any images in pods that reference this ServiceAccount. For components that don't use ServiceAccounts (i.e. grafana, servicegraph, tracing) ImagePullSecrets will be added to the corresponding Deployment(StatefulSet) objects. Must be set for any cluster configured with private docker registry. |
184
184
| global.ingressClass | string |`"higress"`| IngressClass filters which ingress resources the higress controller watches. The default ingress class is higress. There are some special cases for special ingress class. 1. When the ingress class is set as nginx, the higress controller will watch ingress resources with the nginx ingress class or without any ingress class. 2. When the ingress class is set empty, the higress controller will watch all ingress resources in the k8s cluster. |
@@ -203,6 +203,7 @@ The command removes all the Kubernetes components associated with the chart and
203
203
| global.onlyPushRouteCluster | bool |`true`||
204
204
| global.operatorManageWebhooks | bool |`false`| Configure whether Operator manages webhook configurations. The current behavior of Istiod is to manage its own webhook configurations. When this option is set as true, Istio Operator, instead of webhooks, manages the webhook configurations. When this option is set as false, webhooks manage their own webhook configurations. |
205
205
| global.pilotCertProvider | string |`"istiod"`| Configure the certificate provider for control plane communication. Currently, two providers are supported: "kubernetes" and "istiod". As some platforms may not have kubernetes signing APIs, Istiod is the default |
206
+
| global.pluginNamespace | string |`"plugins"`| Namespace for built-in plugin images. Default is "plugins". Used by higress-console to configure plugin image path. |
206
207
| global.priorityClassName | string |`""`| Kubernetes >=v1.11.0 will create two PriorityClass, including system-cluster-critical and system-node-critical, it is better to configure this in order to make sure your Istio pods will not be killed because of low priority class. Refer to https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass for more detail. |
207
208
| global.proxy.autoInject | string |`"enabled"`| This controls the 'policy' in the sidecar injector. |
208
209
| global.proxy.clusterDomain | string |`"cluster.local"`| CAUTION: It is important to ensure that all Istio helm charts specify the same clusterDomain value cluster domain. Default value is "cluster.local". |
0 commit comments