- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 50 for We (0.14 sec)
-
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/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 May 08 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 May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 5.1K bytes - Viewed (0) -
.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) -
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) -
.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) -
.github/ISSUE_TEMPLATE/10_contributor_bug_report.yml
labels: [ "a:bug", "to-triage" ] assignees: [ ] body: - type: markdown attributes: value: | Please follow the instructions below. We receive dozens of issues every week, so to stay productive, we will close issues that don't provide enough information. If you need help with Gradle or have a usage question, please reach [our community](http://help.gradle.org/) instead of creating an issue.
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 3K bytes - Viewed (0)