- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 55 for we (0.14 sec)
-
cni/pkg/nodeagent/informers.go
switch event.Event { case controllers.EventAdd: // pod was added to our cache // we get here in 2 cases: // 1. new pod was created on our node // 2. we were restarted and current existing pods are added to our cache // We have no good way to distinguish between these two cases from here. But we don't need to! // Existing pods will be handled by the dataplane using `GetAmbientPods`,
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 9.6K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/revision-tags.yaml
"reinvocationPolicy" .Values.sidecarInjectorWebhook.reinvocationPolicy "namespace" .Release.Namespace }} {{- define "core" }} {{- /* Kubernetes unfortunately requires a unique name for the webhook in some newer versions, so we assign a unique prefix to each. */}} - name: {{.Prefix}}sidecar-injector.istio.io clientConfig: {{- if .injectionURL }} url: "{{ .injectionURL }}" {{- else }} service:
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 4.4K bytes - Viewed (1) -
cni/pkg/nodeagent/ztunnelserver_test.go
m, fds := readRequest(t, ztunClient) // we got am essage from ztun, so it should have observed us being connected mt.Assert(ztunnelConnected.Name(), nil, monitortest.Exactly(1)) // we should get the fd to dev null. note that we can't assert the fd number // as the kernel may have given us a different number that refers to the same file. assert.Equal(t, len(fds), 1) // in theory we should close the fd, but it's just a test..
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Apr 12 21:47:31 GMT 2024 - 8.6K bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/gateway/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/base/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/istio-operator/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/istio-cni/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/addons/values-kiali.yaml
# We set up anonymous authentication as this is for demos. auth: strategy: anonymous deployment: pod_labels: sidecar.istio.io/inject: "false" accessible_namespaces: - '**' ingress_enabled: false login_token: signing_key: CHANGEME00000000 external_services: # Kiali will not start up without tracing service. We don't want to require it. tracing:
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 09 21:40:53 GMT 2024 - 385 bytes - Viewed (0) -
bin/build_ztunnel.sh
popd } # ztunnel binary vars (TODO handle debug builds, arm, darwin etc.) ISTIO_ZTUNNEL_BASE_URL="${ISTIO_ZTUNNEL_BASE_URL:-https://storage.googleapis.com/istio-build/ztunnel}" # If we are not using the default, assume its private and we need to authenticate if [[ "${ISTIO_ZTUNNEL_BASE_URL}" != "https://storage.googleapis.com/istio-build/ztunnel" ]]; then AUTH_HEADER="Authorization: Bearer $(gcloud auth print-access-token)"
Shell Script - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 21:46:06 GMT 2024 - 5K bytes - Viewed (0)