- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Device (0.21 sec)
-
manifests/charts/gateways/istio-ingress/NOTES.txt
# Port and basic host configuration In order to configure the Service object, the install/upgrade needs to provide a list of all ports. In the past, this was done when installing/upgrading full istio, and involved some duplication - ports configured both in upgrade, Gateway and VirtualService. The new Ingress chart uses a 'values.yaml' (see user-example-ingress), which auto-generates Service ports,
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Apr 15 21:29:06 GMT 2020 - 2K bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/NOTES.txt
-- TLS secrets and domain name management is isolated, for better security -- simplified configuration -- multiple versions of the ingress can be used, to minize upgrade risks - 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
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) -
helm/minio/templates/NOTES.txt
3. mc ls {{ template "minio.fullname" . }}-local {{- end }} {{- if eq .Values.service.type "LoadBalancer" }} MinIO can be accessed via port {{ .Values.service.port }} on an external IP address. Get the service external IP address by: kubectl get svc --namespace {{ .Release.Namespace }} -l app={{ template "minio.fullname" . }}
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 2.7K bytes - Viewed (0)