- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 14 for preact (0.15 sec)
-
manifests/charts/ztunnel/README.md
``` ### Profiles Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets. These can be set with `--set profile=<profile>`. For example, the `demo` profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements. For consistency, the same profiles are used across each chart, even if they do not impact a given chart.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0) -
common-protos/k8s.io/api/batch/v1/generated.proto
// by the 'containerName' field) is not in the set of specified values. // Additional values are considered to be added in the future. Clients should // react to an unknown operator by assuming the requirement is not satisfied. optional string operator = 2; // Specifies the set of values. Each returned container exit code (might be
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 21.1K bytes - Viewed (0) -
cni/pkg/repair/netns.go
return nil, fmt.Errorf("no routes found for %s", ip) } linkIndex := routes[0].LinkIndex return netlink.LinkByIndex(linkIndex) } // getPodNetNs finds the network namespace for a given pod. There is not a great way to do this. Network namespaces live // under the procfs, /proc/<pid>/ns/net. In majority of cases, this is not used directly, but is rather bind mounted to
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Dec 20 22:14:13 GMT 2023 - 4.8K bytes - Viewed (0) -
operator/README.md
## Interaction with controller The controller shares the same API as the operator CLI, so it's possible to install any of the above examples as a CR in the cluster in the istio-system namespace and the controller will react to it with the same outcome as running `istioctl install -f <path-to-custom-resource-file>`. ## Architecture
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sun Sep 17 08:27:52 GMT 2023 - 17.5K bytes - Viewed (0) -
common-protos/k8s.io/api/admissionregistration/v1beta1/generated.proto
// in-cluster DNS as that would be a layering violation). `host` may // also be an IP address. // // Please note that using `localhost` or `127.0.0.1` as a `host` is // risky unless you take great care to run this webhook on all hosts // which run an apiserver which might need to make calls to this // webhook. Such installs are likely to be non-portable, i.e., not easy // to turn up in a new cluster. //
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 22.6K bytes - Viewed (0) -
common-protos/k8s.io/api/admissionregistration/v1/generated.proto
// in-cluster DNS as that would be a layering violation). `host` may // also be an IP address. // // Please note that using `localhost` or `127.0.0.1` as a `host` is // risky unless you take great care to run this webhook on all hosts // which run an apiserver which might need to make calls to this // webhook. Such installs are likely to be non-portable, i.e., not easy // to turn up in a new cluster. //
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 24.4K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/README.md
``` ### Profiles Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets. These can be set with `--set profile=<profile>`. For example, the `demo` profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements. For consistency, the same profiles are used across each chart, even if they do not impact a given chart.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2K bytes - Viewed (0) -
manifests/charts/istio-cni/README.md
``` ### Profiles Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets. These can be set with `--set profile=<profile>`. For example, the `demo` profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements. For consistency, the same profiles are used across each chart, even if they do not impact a given chart.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2.5K bytes - Viewed (0) -
common-protos/k8s.io/api/core/v1/generated.proto
// Those cannot be well described when embedded. // 3. Inconsistent validation. Because the usages are different, the validation rules are different by usage, which makes it hard for users to predict what will happen. // 4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 255.8K bytes - Viewed (0) -
manifests/charts/base/README.md
``` ### Profiles Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets. These can be set with `--set profile=<profile>`. For example, the `demo` profile offers a preset configuration to try out Istio in a test environment, with additional features enabled and lowered resource requirements. For consistency, the same profiles are used across each chart, even if they do not impact a given chart.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0)