- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 252 for gateway (0.17 sec)
-
manifests/charts/gateways/istio-ingress/templates/poddisruptionbudget.yaml
{{- if .Values.global.defaultPodDisruptionBudget.enabled }} {{ $gateway := index .Values "gateways" "istio-ingressgateway" }} apiVersion: policy/v1 kind: PodDisruptionBudget metadata: name: {{ $gateway.name }} namespace: {{ .Release.Namespace }} labels: {{ $gateway.labels | toYaml | trim | indent 4 }} release: {{ .Release.Name }} istio.io/rev: {{ .Values.revision | default "default" | quote }}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 666 bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/templates/serviceaccount.yaml
{{ $gateway := index .Values "gateways" "istio-egressgateway" }} apiVersion: v1 kind: ServiceAccount {{- if .Values.global.imagePullSecrets }} imagePullSecrets: {{- range .Values.global.imagePullSecrets }} - name: {{ . }} {{- end }} {{- end }} metadata: name: {{ $gateway.name }}-service-account namespace: {{ .Release.Namespace }} labels: {{ $gateway.labels | toYaml | trim | indent 4 }} release: {{ .Release.Name }}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 750 bytes - Viewed (0) -
manifests/charts/gateways/istio-egress/NOTES.txt
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. The Gateways use "istio: ingressgateway$SUFFIX" selectors. # Multiple gateway versions # Using different pilot versions # Migration from istio-system
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/gateway/templates/hpa.yaml
kind: HorizontalPodAutoscaler metadata: name: {{ include "gateway.name" . }} namespace: {{ .Release.Namespace }} labels: {{- include "gateway.labels" . | nindent 4 }} annotations: {{- .Values.annotations | toYaml | nindent 4 }} spec: scaleTargetRef: apiVersion: apps/v1 kind: {{ .Values.kind | default "Deployment" }} name: {{ include "gateway.name" . }} minReplicas: {{ .Values.autoscaling.minReplicas }}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sun Feb 18 05:44:12 GMT 2024 - 1.3K bytes - Viewed (0) -
manifests/charts/gateway/templates/role.yaml
{{/*Set up roles for Istio Gateway. Not required for gateway-api*/}} {{- if .Values.rbac.enabled }} apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: {{ include "gateway.serviceAccountName" . }} namespace: {{ .Release.Namespace }} labels: {{- include "gateway.labels" . | nindent 4}} annotations: {{- .Values.annotations | toYaml | nindent 4 }} rules: - apiGroups: [""] resources: ["secrets"]
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Feb 21 16:58:32 GMT 2023 - 963 bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/NOTES.txt
1. Install the new gateway in a new namespace. 2. Copy any TLS certificate to the new namespace, and configure the domains. 3. Checking the new gateway work - for example by overriding the IP in /etc/hosts 4. Modify the DNS server to add the A record of the new namespace 5. Check traffic 6. Delete the A record corresponding to the gateway in istio-system 7. Upgrade istio-system, disabling the ingressgateway
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/istio-control/istio-discovery/templates/clusterrolebinding.yaml
namespace: {{ .Values.global.istioNamespace }} --- {{- if not (eq (toString .Values.pilot.env.PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER) "false") }} apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: istiod-gateway-controller{{- if not (eq .Values.revision "")}}-{{ .Values.revision }}{{- end }}-{{ .Release.Namespace }} labels: app: istiod
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sun Oct 10 17:32:44 GMT 2021 - 1.3K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/istiod-injector-configmap.yaml
sidecar: | {{ .Files.Get "files/injection-template.yaml" | trim | indent 8 }} {{- end }} {{- if not (hasKey .Values.sidecarInjectorWebhook.templates "gateway") }} gateway: | {{ .Files.Get "files/gateway-injection-template.yaml" | trim | indent 8 }} {{- end }} {{- if not (hasKey .Values.sidecarInjectorWebhook.templates "grpc-simple") }} grpc-simple: |
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 3.4K bytes - Viewed (0) -
istioctl/pkg/util/handlers/handlers_test.go
wantNamespace: "istio-system", }, { proxyName: "gateway.gateway.networking.k8s.io/istiod", namespace: "", wantPodName: "gateway.gateway.networking.k8s.io/istiod", wantNamespace: "", }, { proxyName: "gateway.gateway.networking.k8s.io/istiod", namespace: "namespace", wantPodName: "gateway.gateway.networking.k8s.io/istiod", wantNamespace: "namespace", }, {
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Jun 09 18:17:49 GMT 2023 - 6.6K bytes - Viewed (0) -
manifests/charts/README.md
``` ### Gateways A cluster may use multiple Gateways, each with a different load balancer IP, domains and certificates. Since the domain certificates are stored in the gateway namespace, it is recommended to keep each gateway in a dedicated namespace and restrict access. For large-scale gateways it is optionally possible to use a dedicated pilot in the gateway namespace. ### Additional test templates
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)