- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for Namespace (0.18 sec)
-
ci/official/wheel_test/README.md
init files creation process and is subsequently stored in the wheel file after the build. It also contains a few paths that cannot be directly imported. These paths point to attributes or sub-modules within a module's namespace, but they don't correspond to an actual file or directory on the filesystem. The list of such paths is stored in the packages_for_skip variable and will be skipped during the test. ##### How to Build ```
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Aug 31 18:17:57 GMT 2023 - 3.3K bytes - Viewed (0) -
manifests/charts/gateway/README.md
The script below can handle this for you. Replace `RELEASE` and `NAMESPACE` with the name and namespace of the release: ```console KINDS=(service deployment) RELEASE=istio-ingressgateway NAMESPACE=istio-system for KIND in "${KINDS[@]}"; do kubectl --namespace $NAMESPACE --overwrite=true annotate $KIND $RELEASE meta.helm.sh/release-name=$RELEASE
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
manifests/charts/README.md
In the case of the sidecar injector, the namespace label `istio-env: <NAME_OF_ENV>` is used instead of the conventional `istio-injected: true`. The name of the environment is defined as the namespace where the corresponding control plane components (config, discovery, auto-injection) are running. In the examples below, by default this is the `istio-control` namespace. Pod annotations can also be used to select a different 'environment'.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
docs/chroot/README.md
Chroot allows user based namespace isolation on many standard Linux deployments. ## 1. Prerequisites - Familiarity with [chroot](http://man7.org/linux/man-pages/man2/chroot.2.html) - Chroot installed on your machine. ## 2. Install MinIO in Chroot
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 1.7K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/README.md
To install the chart with the release name `istiod`: ```console kubectl create namespace istio-system helm install istiod istio/istiod --namespace istio-system ``` ## Uninstalling the Chart To uninstall/delete the `istiod` deployment: ```console helm delete istiod --namespace istio-system ``` ## Configuration To view support configuration options and documentation, run:
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
Installation in `kube-system` is recommended to ensure the [`system-node-critical`](https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/) `priorityClassName` can be used. You can install in other namespace only on K8S clusters that allow 'system-node-critical' outside of kube-system. ## Configuration To view support configuration options and documentation, run: ```console helm show values istio/istio-cni ```
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) -
manifests/charts/base/README.md
``` _See [helm repo](https://helm.sh/docs/helm/helm_repo/) for command documentation._ ## Installing the Chart To install the chart with the release name `istio-base`: ```console kubectl create namespace istio-system helm install istio-base istio/base -n istio-system ``` ### Profiles Istio Helm charts have a concept of a `profile`, which is a bundled collection of value presets.
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)