- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 27 for value1 (0.23 sec)
-
manifests/helm-profiles/README.md
# Helm Profiles This folder provides a variety of "profiles" for helm installation. While a user can just explicitly pass this with `--values/-f`. However, Istio also provides a feature to bundle these with the charts, which is convenient when installing from remote charts. For details, see `copy-templates` Makefile target, and `manifests/zzz_profile.yaml`. Any changes to this folder should have a `make copy-templates` applied afterwards.
Plain Text - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 708 bytes - Viewed (0) -
cni/README.md
- Pod has `istio-init` initContainer - this indicates a pod running its own injection setup. 1. Return prevResult ## Troubleshooting ### Collecting Logs #### Using `istioctl`/helm - Set: `values.global.logging.level="cni:debug,ambient:debug"` - Inspect the pod logs of a `istio-cni` Daemonset pod on a specific node. #### From a specific node syslog
Plain Text - Registered: Wed May 01 22:53:12 GMT 2024 - Last Modified: Tue Apr 30 22:24:38 GMT 2024 - 12.3K bytes - Viewed (0) -
docs/bucket/notifications/README.md
### Step 1: Add AMQP endpoint to MinIO The AMQP configuration is located under the sub-system `notify_amqp` top-level key. Create a configuration key-value pair here for your AMQP instance. The key is a name for your AMQP endpoint, and the value is a collection of key-value parameters described in the table below. ``` KEY: notify_amqp[:name] publish bucket notifications to AMQP endpoints ARGS:
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
helm/minio/README.md
```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ```
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
docs/throttle/README.md
mc admin service restart myminio/ ``` > NOTE: A zero value of `requests_max` means MinIO will automatically calculate requests based on available RAM size and that is the default behavior. ### Configuring connection (wait) deadline This value works in conjunction with max connection setting, setting this value allows for long waiting requests to quickly time out when there is no slot available to perform the request.
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 2.4K bytes - Viewed (0) -
manifests/charts/gateway/README.md
This chart has the following benefits and differences: * Designed with Helm best practices in mind (standardized values options, values schema, values are not all nested under `gateways.istio-ingressgateway.*`, release name and namespace taken into account, etc).
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
docs/config/README.md
`mc admin config set alias/ delay=15.0`. By default the value is `10.0`. This means the scanner will sleep *10x* the time each operation takes. In most setups this will keep the scanner slow enough to not impact overall system performance. Setting the `delay` key to a *lower* value will make the scanner faster and setting it to 0 will make the scanner run at full speed (not recommended in production). Setting it to a higher value will make the scanner slower, consuming less resources with...
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Mon Sep 11 21:48:54 GMT 2023 - 17.7K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
The command will generate the `scrape_configs` section of the prometheus.yml as follows: ##### Cluster
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
operator/README.md
charts unmodified (but validated through a [schema](pkg/apis/istio/v1alpha1/values_types.proto)). Values.yaml settings are overridden the same way as the new API, though a customized CR overlaid over default values for the selected profile. Here's an example of overriding some global level default values ([samples/values-global.yaml](samples/values-global.yaml)): ```yaml apiVersion: install.istio.io/v1alpha1 kind: IstioOperator spec:
Plain Text - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Sun Sep 17 08:27:52 GMT 2023 - 17.5K bytes - Viewed (0) -
manifests/charts/ztunnel/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`. When configuring the chart, you should not include this.
Plain Text - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0)