- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 79 for as (0.14 sec)
-
manifests/charts/gateway/values.yaml
# For example, to set the `unhealthyPodEvictionPolicy` to `AlwaysAllow`, you can update this value as follows: # # podDisruptionBudget: # minAvailable: 1 # unhealthyPodEvictionPolicy: AlwaysAllow # # To disable the PodDisruptionBudget, you can leave it as an empty object `{}`: # # podDisruptionBudget: {} # podDisruptionBudget: {}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jan 11 16:55:28 GMT 2024 - 4.4K bytes - Viewed (0) -
docs/en/data/sponsors.yml
- url: https://databento.com/ title: Pay as you go for market data img: https://fastapi.tiangolo.com/img/sponsors/databento.svg - url: https://speakeasyapi.dev?utm_source=fastapi+repo&utm_medium=github+sponsorship title: SDKs for your API | Speakeasy img: https://fastapi.tiangolo.com/img/sponsors/speakeasy.png - url: https://www.svix.com/ title: Svix - Webhooks as a service
Others - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Mon Mar 25 23:10:11 GMT 2024 - 3.3K bytes - Viewed (0) -
manifests/charts/istiod-remote/templates/configmap.yaml
trustDomain: "cluster.local" # The namespace to treat as the administrative root namespace for Istio configuration. # When processing a leaf namespace Istio will search for declarations in that namespace first # and if none are found it will search in the root namespace. Any matching declaration found in the root namespace # is processed as if it were declared in the leaf namespace.
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 4.9K bytes - Viewed (0) -
.github/workflows/issue-manager.yml
Others - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 30 18:46:56 GMT 2024 - 1.1K bytes - Viewed (0) -
helm-releases/minio-5.1.0.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* ### Existing PersistentVolumeClai If a Persistent Volume Claim already exists, specify it during installation. 1....
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Mar 03 18:49:37 GMT 2024 - 21.3K bytes - Viewed (0) -
manifests/charts/base/crds/crd-all.gen.yaml
format: int32 type: integer minHealthPercent: description: Outlier detection will be enabled as long as the associated load balancing pool has at least min_health_percent hosts in healthy mode. format: int32 type: integer
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Apr 22 20:20:47 GMT 2024 - 606.1K bytes - Viewed (0) -
helm-releases/minio-5.0.15.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* ### Existing PersistentVolumeClai If a Persistent Volume Claim already exists, specify it during installation. 1....
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Jan 12 18:18:57 GMT 2024 - 20.8K bytes - Viewed (0) -
manifests/charts/gateway/templates/zzz_profile.yaml
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). We can then merge the profile onto the defaults, then the user settings onto that.
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
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). We can then merge the profile onto the defaults, then the user settings onto that.
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
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). We can then merge the profile onto the defaults, then the user settings onto that.
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)