commit 11cc797922

Author: iwilltry42 <iwilltry42@gmail.com>
Date:   Wed Oct 7 08:58:03 2020 +0200

    overall/logging: new trace log level

    - new root flag '--trace' with precedence over '--verbose'
    - some new trace logs
    - migrated some debug logs to trace logs to reduce debug verbosity

faq/faq/index.html

@@ -579,7 +579,6 @@
 </ul>
 <div class="highlight"><pre><span></span><code>starting kubernetes: preparing server: start cluster and https: raft_init<span class="o">()</span>: io: create I/O capabilities probe file: posix_allocate: operation not supported on socket
 </code></pre></div>
-
 <ul>
 <li>This issue can be worked around by providing docker with a different filesystem (that&rsquo;s also better for docker-in-docker stuff).</li>
 <li>A possible solution can be found here: <a href="https://github.com/rancher/k3s/issues/1688#issuecomment-619570374">https://github.com/rancher/k3s/issues/1688#issuecomment-619570374</a></li>

index.html

@@ -646,15 +646,12 @@
 <p>Create a cluster named <code>mycluster</code> with just a single server node:</p>
 <div class="highlight"><pre><span></span><code>k3d cluster create mycluster
 </code></pre></div>
-
 <p>Get the new cluster&rsquo;s connection details merged into your default kubeconfig (usually specified using the <code>KUBECONFIG</code> environment variable or the default path <code class="highlight"><span class="nv">$HOME</span>/.kube/config</code>) and directly switch to the new context:</p>
 <div class="highlight"><pre><span></span><code>k3d kubeconfig merge mycluster --switch-context
 </code></pre></div>
-
 <p>Use the new cluster with <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl/"><code>kubectl</code></a>, e.g.:</p>
 <div class="highlight"><pre><span></span><code>kubectl get nodes
 </code></pre></div>
-
 <h2 id="related-projects">Related Projects<a class="headerlink" href="#related-projects" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://github.com/inercia/k3x">k3x</a>: a graphics interface (for Linux) to k3d.</li>

sitemap.xml

@@ -1,43 +1,43 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url>
      <loc>https://k3d.io/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/usage/commands/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/usage/kubeconfig/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/usage/multiserver/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/usage/guides/exposing_services/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/usage/guides/registries/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/internals/defaults/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/internals/networking/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/faq/faq/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url><url>
      <loc>https://k3d.io/faq/v1vsv3-comparison/</loc>
-     <lastmod>2020-10-06</lastmod>
+     <lastmod>2020-10-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
 </urlset>

usage/guides/exposing_services/index.html

@@ -566,7 +566,6 @@ Therefore, we have to create the cluster in a way, that the internal port 80 (wh
           <span class="nt">serviceName</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">nginx</span>
           <span class="nt">servicePort</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">80</span>
 </code></pre></div>
-
 </li>
 <li>
 <p>Curl it via localhost</p>
@@ -609,7 +608,6 @@ Therefore, we have to create the cluster in a way, that the internal port 80 (wh
     <span class="nt">app</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">nginx</span>
   <span class="nt">type</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">NodePort</span>
 </code></pre></div>
-
 </li>
 <li>
 <p>Curl it via localhost</p>

usage/guides/registries/index.html

@@ -645,7 +645,6 @@
     <span class="nt">endpoint</span><span class="p">:</span>
       <span class="p p-Indicator">-</span> <span class="l l-Scalar l-Scalar-Plain">http://my.company.registry:5000</span>
 </code></pre></div>
-
 <p>In this example, an image with a name like <code>my.company.registry:5000/nginx:latest</code> would be
 <em>pulled</em> from the registry running at <code>http://my.company.registry:5000</code>.</p>
 <p>Note well there is an important limitation: <strong>this configuration file will only work with k3s &gt;= v0.10.0</strong>. It will fail silently with previous versions of k3s, but you find in the <a href="#k3s-old">section below</a> an alternative solution.</p>
@@ -664,7 +663,6 @@
       <span class="nt">username</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">aladin</span>
       <span class="nt">password</span><span class="p">:</span> <span class="l l-Scalar l-Scalar-Plain">abracadabra</span>
 </code></pre></div>
-
 <h3 id="secure-registries">Secure registries<a class="headerlink" href="#secure-registries" title="Permanent link">&para;</a></h3>
 <p>When using secure registries, the <a href="#registries-file"><code>registries.yaml</code> file</a> must include information about the certificates. For example, if you want to use images from the secure registry running at <code>https://my.company.registry</code>, you must first download a CA file valid for that server and store it in some well-known directory like <code>${HOME}/.k3d/my-company-root.pem</code>.  </p>
 <p>Then you have to mount the CA file in some directory in the nodes in the cluster and include that mounted file in a <code>configs</code> section in the <a href="#registries-file"><code>registries.yaml</code> file</a>.
@@ -680,7 +678,6 @@ For example, if we mount the CA file in <code>/etc/ssl/certs/my-company-root.pem
       <span class="c1"># we will mount &quot;my-company-root.pem&quot; in the /etc/ssl/certs/ directory.</span>
       <span class="nt">ca_file</span><span class="p">:</span> <span class="s">&quot;/etc/ssl/certs/my-company-root.pem&quot;</span>
 </code></pre></div>
-
 <p>Finally, we can create the cluster, mounting the CA file in the path we specified in <code>ca_file</code>:</p>
 <p><code class="highlight">k3d cluster create --volume <span class="s2">&quot;</span><span class="si">${</span><span class="nv">HOME</span><span class="si">}</span><span class="s2">/.k3d/my-registries.yaml:/etc/rancher/k3s/registries.yaml&quot;</span> --volume <span class="s2">&quot;</span><span class="si">${</span><span class="nv">HOME</span><span class="si">}</span><span class="s2">/.k3d/my-company-root.pem:/etc/ssl/certs/my-company-root.pem&quot;</span></code></p>
 <h2 id="using-a-local-registry">Using a local registry<a class="headerlink" href="#using-a-local-registry" title="Permanent link">&para;</a></h2>
@@ -694,7 +691,6 @@ For example, if we mount the CA file in <code>/etc/ssl/certs/my-company-root.pem
 <div class="highlight"><pre><span></span><code>docker volume create local_registry
 docker container run -d --name registry.localhost -v local_registry:/var/lib/registry --restart always -p <span class="m">5000</span>:5000 registry:2
 </code></pre></div>
-
 <p>These commands will start your registry in <code>registry.localhost:5000</code>. In order to push to this registry, you will need to make it accessible as described in the next section.
 Once your registry is up and running, we will need to add it to your <code>registries.yaml</code> configuration file.
 Finally, you have to connect the registry network to the k3d cluster network: <code class="highlight">docker network connect k3d-k3s-default registry.localhost</code>. And then you can <a href="#testing-your-registry">test your local registry</a>.</p>
@@ -706,7 +702,6 @@ Otherwise, it&rsquo;s installable using <code>sudo apt install libnss-myhostname
 <p>If it&rsquo;s not the case, you can add an entry in your <code>/etc/hosts</code> file like this:</p>
 <div class="highlight"><pre><span></span><code><span class="m">127</span>.0.0.1 registry.localhost
 </code></pre></div>
-
 <p>Once again, this will only work with k3s &gt;= v0.10.0 (see the some sections below when using k3s &lt;= v0.9.1)</p>
 <h2 id="testing-your-registry">Testing your registry<a class="headerlink" href="#testing-your-registry" title="Permanent link">&para;</a></h2>
 <p>You should test that you can</p>

usage/multiserver/index.html

@@ -521,12 +521,10 @@
 The first server to be created will use the <code>--cluster-init</code> flag and k3d will wait for it to be up and running before creating (and connecting) the other server nodes.</p>
 <div class="highlight"><pre><span></span><code>    k3d cluster create multiserver --servers <span class="m">3</span>
 </code></pre></div>
-
 <h2 id="adding-server-nodes-to-a-running-cluster">Adding server nodes to a running cluster<a class="headerlink" href="#adding-server-nodes-to-a-running-cluster" title="Permanent link">&para;</a></h2>
 <p>In theory (and also in practice in most cases), this is as easy as executing the following command:</p>
 <div class="highlight"><pre><span></span><code>    k3d node create newserver --cluster multiserver --role server
 </code></pre></div>
-
 <div class="admonition important">
 <p class="admonition-title">There&rsquo;s a trap!</p>
 <p>If your cluster was initially created with only a single server node, then this will fail.