mirror of https://github.com/istio/istio.io.git
fix typo sufficent-->sufficient (#13429)
Signed-off-by: yanggang <gang.yang@daocloud.io>
This commit is contained in:
parent
7a601523c9
commit
b781e84053
File diff suppressed because one or more lines are too long
|
|
@ -24,7 +24,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -24,7 +24,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.11/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -24,7 +24,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.12/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.13/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.14/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.15/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.16/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.26.1
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.17/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -21,7 +21,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.14.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.2/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube:</p><pre><code class=language-bash data-expandlinks=true>$ minikube ssh
|
||||
$ top
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -5,7 +5,7 @@ AKS You can create an AKS cluster via the az cli or the Azure portal.
|
|||
For the az cli option, complete az login authentication OR use cloud shell, then run the following commands below.
|
||||
Determine the desired region name which supports AKS</description></item><item><title>Docker Desktop</title><link>/v1.3/docs/setup/platform-setup/docker/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/v1.3/docs/setup/platform-setup/docker/</guid><description>To run Istio with Docker Desktop, install a version which contains a supported Kubernetes version (1.13, 1.14, 1.15).
|
||||
If you want to run Istio under Docker Desktop&rsquo;s built-in Kubernetes, you need to increase Docker&rsquo;s memory limit under the Advanced pane of Docker Desktop&rsquo;s preferences. Set the resources to 8.0 GB of memory and 4 CPUs.
|
||||
Docker Preferences Minimum memory requirements vary. 8 GB is sufficent to run Istio and Bookinfo.</description></item><item><title>Google Kubernetes Engine</title><link>/v1.3/docs/setup/platform-setup/gke/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/v1.3/docs/setup/platform-setup/gke/</guid><description>Google offers an add-on for GKE, which you can use instead of installing Istio manually. To determine if the add-on is right for you, refer to Istio on GKE for more information. Follow these instructions to prepare a GKE cluster for Istio.
|
||||
Docker Preferences Minimum memory requirements vary. 8 GB is sufficient to run Istio and Bookinfo.</description></item><item><title>Google Kubernetes Engine</title><link>/v1.3/docs/setup/platform-setup/gke/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/v1.3/docs/setup/platform-setup/gke/</guid><description>Google offers an add-on for GKE, which you can use instead of installing Istio manually. To determine if the add-on is right for you, refer to Istio on GKE for more information. Follow these instructions to prepare a GKE cluster for Istio.
|
||||
To enable SDS in Istio, use Kubernetes 1.13 or above. Create a new cluster.
|
||||
$ gcloud container clusters create &lt;cluster-name&gt; \ --cluster-version latest \ --num-nodes 4 \ --zone &lt;zone&gt; \ --project &lt;project-id&gt; To use the Istio CNI feature, the network-policy GKE feature must be enabled in the cluster.</description></item><item><title>IBM Cloud</title><link>/v1.3/docs/setup/platform-setup/ibm/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/v1.3/docs/setup/platform-setup/ibm/</guid><description>Follow these instructions to prepare a cluster for Istio using the IBM Cloud Kubernetes Service. To install Istio on IBM Cloud Private, refer to Istio on IBM Cloud Private instead.
|
||||
IBM offers a managed control plane add-on for the IBM Cloud Kubernetes Service, which you can use instead of installing Istio manually. Refer to Istio on IBM Cloud Kubernetes Service for details and instructions. To prepare a cluster before manually installing Istio, proceed as follows:</description></item><item><title>Kubernetes Gardener</title><link>/v1.3/docs/setup/platform-setup/gardener/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/v1.3/docs/setup/platform-setup/gardener/</guid><description>Bootstrapping Gardener To set up your own Gardener, see the documentation or have a look at the landscape-setup-template project. To learn more about this open source project, read the blog on kubernetes.io.
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.14.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.3/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
$ top
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -22,7 +22,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.14.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.4/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
$ top
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -23,7 +23,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.14.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.5/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
$ top
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -23,7 +23,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.14.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.5/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
$ top
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -22,7 +22,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.17.5
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.6/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.17.5
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.7/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.18.10
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.8/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -25,7 +25,7 @@ within the minikube configuration using the following command:</p><pre><code cla
|
|||
You can change the version to any Kubernetes version supported by Istio by altering the
|
||||
<code>--kubernetes-version</code> value:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube start --memory=16384 --cpus=4 --kubernetes-version=v1.20.2
|
||||
</code></pre><p>Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 <code>MB</code> is sufficient to run
|
||||
Istio and bookinfo.</p><div><aside class="callout tip"><div class=type><svg class="large-icon"><use xlink:href="/v1.9/img/icons.svg#callout-tip"/></svg></div><div class=content><p>If you don’t have enough RAM allocated to the minikube
|
||||
virtual machine, the following errors could occur:</p><ul><li>image pull failures</li><li>healthcheck timeout failures</li><li>kubectl failures on the host</li><li>general network instability of the virtual machine and the host</li><li>complete lock-up of the virtual machine</li><li>host NMI watchdog reboots</li></ul><p>One effective way to monitor memory usage in minikube is to <code>ssh</code> into the minikube virtual machine
|
||||
and from that prompt run the top command:</p><pre><code class=language-bash data-expandlinks=true data-repo=istio>$ minikube ssh
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ test: no
|
|||
{{< image width="60%" link="./dockerprefs.png" caption="Docker Preferences" >}}
|
||||
|
||||
{{< warning >}}
|
||||
Minimum memory requirements vary. 8 `GB` is sufficent to run
|
||||
Minimum memory requirements vary. 8 `GB` is sufficient to run
|
||||
Istio and Bookinfo. If you don't have enough memory allocated in Docker Desktop,
|
||||
the following errors could occur:
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ Refer to the [`api-server` reference docs](https://kubernetes.io/docs/reference/
|
|||
{{< /text >}}
|
||||
|
||||
Depending on the hypervisor you use and the platform on which the hypervisor
|
||||
is run, minimum memory requirements vary. 16384 `MB` is sufficent to run
|
||||
is run, minimum memory requirements vary. 16384 `MB` is sufficient to run
|
||||
Istio and bookinfo.
|
||||
|
||||
{{< tip >}}
|
||||
|
|
|
|||
Loading…
Reference in New Issue