- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for DEPLOY (0.6 sec)
-
manifests/charts/gateway/templates/NOTES.txt
$ helm status {{ .Release.Name }} -n {{ .Release.Namespace }} $ helm get all {{ .Release.Name }} -n {{ .Release.Namespace }} Next steps: * Deploy an HTTP Gateway: https://istio.io/latest/docs/tasks/traffic-management/ingress/ingress-control/
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Apr 17 02:27:41 GMT 2024 - 452 bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/NOTES.txt
{{- if (eq .Values.profile "ambient") }} * Get started with ambient: https://istio.io/latest/docs/ops/ambient/getting-started/ * Review ambient's architecture: https://istio.io/latest/docs/ops/ambient/architecture/ {{- else }} * Deploy a Gateway: https://istio.io/latest/docs/setup/additional-setup/gateway/ * Try out our tasks to get started on common configurations: * https://istio.io/latest/docs/tasks/traffic-management
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Apr 17 16:38:47 GMT 2024 - 4.2K bytes - Viewed (1) -
manifests/charts/README.md
Goals: - Improve upgrade experience: users should be able to gradually roll upgrades, with proper canary deployments for Istio components. It should be possible to deploy a new version while keeping the stable version in place and gradually migrate apps to the new version. - More flexibility: the new installer allows multiple 'environments', allowing applications to select
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/NOTES.txt
- the new chart uses the default namespace service account, and doesn't require additional RBAC permissions. - simplified label structure. Label change is not supported on upgrade. - for 'internal load balancer' you should deploy a separate gateway, in a different namespace. All ingress gateway have a "app:ingressgateway" label, used to identify it as an ingress, and an "istio: ingressgateway$SUFFIX" label of Gateway selection.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Apr 15 21:29:06 GMT 2020 - 1.5K bytes - Viewed (0) -
manifests/charts/istio-cni/values.yaml
excludeNamespaces: - kube-system # Allows user to set custom affinity for the DaemonSet affinity: {} # Custom annotations on pod level, if you need them podAnnotations: {} # Deploy the config files as plugin chain (value "true") or as standalone files in the conf dir (value "false")? # Some k8s flavors (e.g. OpenShift) do not support the chain approach, set to false if this is the case chained: true
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 30 22:24:38 GMT 2024 - 5.2K bytes - Viewed (1) -
manifests/charts/istio-cni/templates/daemonset.yaml
name: istio-cni-config key: cni_network_config - name: CNI_NET_DIR value: {{ default "/etc/cni/net.d" .Values.cni.cniConfDir }} # Deploy as a standalone CNI plugin or as chained? - name: CHAINED_CNI_PLUGIN value: "{{ .Values.cni.chained }}" - name: REPAIR_ENABLED value: "{{ .Values.cni.repair.enabled }}"
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 9.4K bytes - Viewed (0)