Skip to content

Commit

Permalink
Deployed c0c9059 to main with MkDocs 1.5.3 and mike 2.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions committed Apr 21, 2024
1 parent a819cd2 commit d9d9539
Show file tree
Hide file tree
Showing 4 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion main/getting-started/getting-started/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
<span class=w> </span><span class=nt>addToKnownHosts</span><span class=p>:</span><span class=w> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
<span class=w> </span><span class=nt>os</span><span class=p>:</span>
<span class=w> </span><span class=nt>distro</span><span class=p>:</span><span class=w> </span><span class="l l-Scalar l-Scalar-Plain">ubuntu22</span>
</code></pre></div> <h3 id=step-33-cluster-nodes>Step 3.3 - Cluster nodes<a class=headerlink href=#step-33-cluster-nodes title="Anchor link">&#128279;&#xFE0E;</a></h3> <p>In the <code>nodes</code> subsection, we <strong>define all nodes that will form the cluster</strong>. Each node can be defined as one of the following three types:</p> <ul> <li> <p><code>worker</code></p> <p>A worker node runs the applications and workloads that are deployed in the cluster. It communicates with the master node to receive instructions on how to schedule and run the containers.</p> </li> <li> <p><code>master</code></p> <p>Master nodes are responsible for managing and coordinating the worker nodes in the cluster. Therefore, <strong>each cluster must contain at least one master node</strong>.</p> <p>Since etcd key-value datastore is also present on these nodes, the number of master nodes must be odd. For more information, see <a href=https://etcd.io/docs/v3.4/faq/#why-an-odd-number-of-cluster-members>etcd FAQ</a>.</p> </li> <li> <p><code>loadBalancer</code></p> <p>These nodes server as internal load balancers that expose the Kubernetes control plane at a single endpoint. They are essential when more then one master node is configured in the cluster.</p> </li> </ul> <p>This guide is focused on deploying a Kubernetes cluster with only one master node, which eliminates the need for internal load balancers. However, if you are interested in creating a <a href=../../examples/multi-master-cluster>multi-master</a> or <a href=../../examples/ha-cluster>high-availability (HA)</a> cluster, please refer to the corresponding examples.</p> <p>To better understand this part, let's take a look at an example configuration:</p> <div class=highlight><span class=filename>kubitect.yaml</span><pre><span></span><code><span class=nt>cluster</span><span class=p>:</span>
</code></pre></div> <h3 id=step-33-cluster-nodes>Step 3.3 - Cluster nodes<a class=headerlink href=#step-33-cluster-nodes title="Anchor link">&#128279;&#xFE0E;</a></h3> <p>In the <code>nodes</code> subsection, we <strong>define all nodes that will form the cluster</strong>. Each node can be defined as one of the following three types:</p> <ul> <li> <p><code>worker</code></p> <p>A worker node runs the applications and workloads that are deployed in the cluster. It communicates with the master node to receive instructions on how to schedule and run the containers.</p> </li> <li> <p><code>master</code></p> <p>Master nodes are responsible for managing and coordinating the worker nodes in the cluster. Therefore, <strong>each cluster must contain at least one master node</strong>.</p> <p>Since etcd key-value datastore is also present on these nodes, the number of master nodes must be odd. For more information, see <a href=https://etcd.io/docs/v3.4/faq/#why-an-odd-number-of-cluster-members>etcd FAQ</a>.</p> </li> <li> <p><code>loadBalancer</code></p> <p>These nodes serve as external load balancers that expose the Kubernetes control plane at a single endpoint. They are required when more then one master node is configured in the cluster.</p> </li> </ul> <p>This guide is focused on deploying a Kubernetes cluster with a single master node. However, if you are interested in creating a <a href=../../examples/multi-master-cluster>multi-master</a> or <a href=../../examples/ha-cluster>high-availability (HA)</a> cluster, please refer to the corresponding examples.</p> <p>To better understand this part, let's take a look at an example configuration:</p> <div class=highlight><span class=filename>kubitect.yaml</span><pre><span></span><code><span class=nt>cluster</span><span class=p>:</span>
<span class=w> </span><span class="l l-Scalar l-Scalar-Plain">...</span>
<span class=w> </span><span class="l l-Scalar l-Scalar-Plain">nodes</span><span class="p p-Indicator">:</span>
<span class=w> </span><span class=nt>master</span><span class=p>:</span>
Expand Down
2 changes: 1 addition & 1 deletion main/getting-started/installation/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
</code></pre></div>
--> <p>Verify the installation by checking the Kubitect version. <div class=highlight><pre><span></span><code>kubitect<span class=w> </span>--version

<span class=c1># kubitect version v3.3.1</span>
<span class=c1># kubitect version v3.4.0</span>
</code></pre></div></p> <h2 id=enable-shell-autocomplete>Enable shell autocomplete<a class=headerlink href=#enable-shell-autocomplete title="Anchor link">&#128279;&#xFE0E;</a></h2> <div class="admonition tip"> <p class=admonition-title>Tip</p> <p>To list all supported shells, run: <code>kubitect completion -h</code></p> <p>For shell specific instructions run: <code> kubitect completion <em>shell</em> -h </code></p> </div> <div class="tabbed-set tabbed-alternate" data-tabs=1:2><input checked=checked id=__tabbed_1_1 name=__tabbed_1 type=radio><input id=__tabbed_1_2 name=__tabbed_1 type=radio><div class=tabbed-labels><label for=__tabbed_1_1>Bash</label><label for=__tabbed_1_2>Zsh</label></div> <div class=tabbed-content> <div class=tabbed-block> <p>This script depends on the <code>bash-completion</code> package. If it is not installed already, you can install it via your OS's package manager.</p> <p>To load completions in your current shell session:</p> <div class=highlight><pre><span></span><code><span class=nb>source</span><span class=w> </span>&lt;<span class=o>(</span>kubitect<span class=w> </span>completion<span class=w> </span>bash<span class=o>)</span>
</code></pre></div> <p>To load completions for every new session, execute once:</p> <p><strong>Linux:</strong></p> <div class=highlight><pre><span></span><code>kubitect<span class=w> </span>completion<span class=w> </span>bash<span class=w> </span>&gt;<span class=w> </span>/etc/bash_completion.d/kubitect
</code></pre></div> <p><strong>macOS:</strong></p> <div class=highlight><pre><span></span><code>kubitect<span class=w> </span>completion<span class=w> </span>bash<span class=w> </span>&gt;<span class=w> </span><span class=k>$(</span>brew<span class=w> </span>--prefix<span class=k>)</span>/etc/bash_completion.d/kubitect
Expand Down
2 changes: 1 addition & 1 deletion main/search/search_index.json

Large diffs are not rendered by default.

Binary file modified main/sitemap.xml.gz
Binary file not shown.

0 comments on commit d9d9539

Please sign in to comment.