- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 60 for we (0.13 sec)
-
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 Mar 20 22:53:08 GMT 2024 - Last Modified: Thu Jan 18 16:33:33 GMT 2024 - 1.3K 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 Mar 20 22:53:08 GMT 2024 - Last Modified: Thu Jan 18 16:33:33 GMT 2024 - 1.3K 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 Apr 24 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 Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/feature_addition_request.yaml
just a feature that seems like a sensible addition to Guava? Before new features get added to Guava, we really want to be sure that it's for a use case that actually comes up in the real world. We want to hear the real-world use case so the community can discuss and debate whether this feature is actually the *best* way to address
Others - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Fri Nov 17 18:47:47 GMT 2023 - 5.8K bytes - Viewed (0) -
manifests/charts/istiod-remote/templates/services.yaml
apiVersion: v1 kind: Service metadata: {{- if .Values.pilot.enabled }} # when local istiod is enabled, we can't use istiod service name to reach the remote control plane name: istiod{{- if .Values.revision }}-{{ .Values.revision}}{{- end }}-remote {{- else }} # when local istiod isn't enabled, we can use istiod service name to reach the remote control plane name: istiod{{- if .Values.revision }}-{{ .Values.revision}}{{- end }}
Others - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Fri Feb 02 17:36:40 GMT 2024 - 1.1K bytes - Viewed (0) -
manifests/charts/istiod-remote/templates/mutatingwebhook.yaml
{{- /* Core defines the common configuration used by all webhook segments */}} {{/* Copy just what we need to avoid expensive deepCopy */}} {{- $whv := dict "revision" .Values.revision "injectionPath" .Values.istiodRemote.injectionPath "injectionURL" .Values.istiodRemote.injectionURL "reinvocationPolicy" .Values.sidecarInjectorWebhook.reinvocationPolicy "caBundle" .Values.istiodRemote.injectionCABundle "namespace" .Release.Namespace }}
Others - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Thu Mar 07 06:39:27 GMT 2024 - 5.1K bytes - Viewed (0) -
helm/minio/templates/_helpers.tpl
proper Docker Image Registry Secret Names */}} {{- define "minio.imagePullSecrets" -}} {{/* Helm 2.11 supports the assignment of a value to a variable defined in a different scope, but Helm 2.9 and 2.10 does not support it, so we need to implement this if-else logic. Also, we can not use a single if because lazy evaluation is not an option */}} {{- if .Values.global }} {{- if .Values.global.imagePullSecrets }} imagePullSecrets: {{- range .Values.global.imagePullSecrets }} - name: {{ . }} {{- end }}...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Apr 17 06:04:15 GMT 2023 - 6.5K bytes - Viewed (2) -
.github/ISSUE_TEMPLATE/00-bug.yml
- type: input id: go-version attributes: label: Go version description: | What version of Go are you using (`go version`)? Note: we only [support](https://go.dev/doc/devel/release#policy) the two most recent major releases. placeholder: ex. go version go1.20.7 darwin/arm64 validations: required: true - type: textarea id: go-env
Others - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Jan 04 23:31:17 GMT 2024 - 3.3K bytes - Viewed (0) -
.github/workflows/contributor-pr.yml
name: Contributor CI Build on: push: branches: - master pull_request: branches: - master concurrency: # On master/release, we don't want any jobs cancelled so the sha is used to name the group # On PR branches, we cancel the job if new commits are pushed
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 3.9K bytes - Viewed (0)