deploy: 71ab51a

index.html

@@ -229,16 +229,16 @@ <h3 id="gitops"><a class="header" href="#gitops">GitOps</a></h3>
 <p><a href="https://github.com/renovatebot/renovate">Renovate</a> watches my <strong>entire</strong> repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged <a href="https://github.com/fluxcd/flux2">Flux</a> applies the changes to my cluster.</p>
 <h3 id="directories"><a class="header" href="#directories">Directories</a></h3>
 <p>This Git repository contains the following directories under <a href="./kubernetes/">Kubernetes</a>.</p>
-<pre><code class="language-sh"> kubernetes
-├──  main # main cluster
-│ ├──  apps # applications
-│ ├──  bootstrap # bootstrap procedures
-│ ├──  flux # core flux configuration
-│ └──  templates # re-useable components
-└──  storage # storage cluster
- ├──  apps # applications
- ├──  bootstrap # bootstrap procedures
- └──  flux # core flux configuration
+<pre><code class="language-sh">📁 kubernetes
+├── 📁 main # main cluster
+│ ├── 📁 apps # applications
+│ ├── 📁 bootstrap # bootstrap procedures
+│ ├── 📁 flux # core flux configuration
+│ └── 📁 templates # re-useable components
+└── 📁 storage # storage cluster
+ ├── 📁 apps # applications
+ ├── 📁 bootstrap # bootstrap procedures
+ └── 📁 flux # core flux configuration
 </code></pre>
 <h3 id="cluster-layout"><a class="header" href="#cluster-layout">Cluster Layout</a></h3>
 <p>Below is a high-level look at the layout of how my directory structure with Flux works. In this brief example, you are able to see that <code>authelia</code> will not be able to run until <code>lldap</code> and <code>cloudnative-pg</code> are running. It also shows that the <code>Cluster</code> custom resource depends on the <code>cloudnative-pg</code> Helm chart. This is needed because <code>cloudnative-pg</code> installs the <code>Cluster</code> custom resource definition in the Helm chart.</p>

introduction.html

@@ -229,16 +229,16 @@ <h3 id="gitops"><a class="header" href="#gitops">GitOps</a></h3>
 <p><a href="https://github.com/renovatebot/renovate">Renovate</a> watches my <strong>entire</strong> repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged <a href="https://github.com/fluxcd/flux2">Flux</a> applies the changes to my cluster.</p>
 <h3 id="directories"><a class="header" href="#directories">Directories</a></h3>
 <p>This Git repository contains the following directories under <a href="./kubernetes/">Kubernetes</a>.</p>
-<pre><code class="language-sh"> kubernetes
-├──  main # main cluster
-│ ├──  apps # applications
-│ ├──  bootstrap # bootstrap procedures
-│ ├──  flux # core flux configuration
-│ └──  templates # re-useable components
-└──  storage # storage cluster
- ├──  apps # applications
- ├──  bootstrap # bootstrap procedures
- └──  flux # core flux configuration
+<pre><code class="language-sh">📁 kubernetes
+├── 📁 main # main cluster
+│ ├── 📁 apps # applications
+│ ├── 📁 bootstrap # bootstrap procedures
+│ ├── 📁 flux # core flux configuration
+│ └── 📁 templates # re-useable components
+└── 📁 storage # storage cluster
+ ├── 📁 apps # applications
+ ├── 📁 bootstrap # bootstrap procedures
+ └── 📁 flux # core flux configuration
 </code></pre>
 <h3 id="cluster-layout"><a class="header" href="#cluster-layout">Cluster Layout</a></h3>
 <p>Below is a high-level look at the layout of how my directory structure with Flux works. In this brief example, you are able to see that <code>authelia</code> will not be able to run until <code>lldap</code> and <code>cloudnative-pg</code> are running. It also shows that the <code>Cluster</code> custom resource depends on the <code>cloudnative-pg</code> Helm chart. This is needed because <code>cloudnative-pg</code> installs the <code>Cluster</code> custom resource definition in the Helm chart.</p>

print.html

@@ -230,16 +230,16 @@ <h3 id="gitops"><a class="header" href="#gitops">GitOps</a></h3>
 <p><a href="https://github.com/renovatebot/renovate">Renovate</a> watches my <strong>entire</strong> repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged <a href="https://github.com/fluxcd/flux2">Flux</a> applies the changes to my cluster.</p>
 <h3 id="directories"><a class="header" href="#directories">Directories</a></h3>
 <p>This Git repository contains the following directories under <a href="./kubernetes/">Kubernetes</a>.</p>
-<pre><code class="language-sh"> kubernetes
-├──  main # main cluster
-│ ├──  apps # applications
-│ ├──  bootstrap # bootstrap procedures
-│ ├──  flux # core flux configuration
-│ └──  templates # re-useable components
-└──  storage # storage cluster
- ├──  apps # applications
- ├──  bootstrap # bootstrap procedures
- └──  flux # core flux configuration
+<pre><code class="language-sh">📁 kubernetes
+├── 📁 main # main cluster
+│ ├── 📁 apps # applications
+│ ├── 📁 bootstrap # bootstrap procedures
+│ ├── 📁 flux # core flux configuration
+│ └── 📁 templates # re-useable components
+└── 📁 storage # storage cluster
+ ├── 📁 apps # applications
+ ├── 📁 bootstrap # bootstrap procedures
+ └── 📁 flux # core flux configuration
 </code></pre>
 <h3 id="cluster-layout"><a class="header" href="#cluster-layout">Cluster Layout</a></h3>
 <p>Below is a high-level look at the layout of how my directory structure with Flux works. In this brief example, you are able to see that <code>authelia</code> will not be able to run until <code>lldap</code> and <code>cloudnative-pg</code> are running. It also shows that the <code>Cluster</code> custom resource depends on the <code>cloudnative-pg</code> Helm chart. This is needed because <code>cloudnative-pg</code> installs the <code>Cluster</code> custom resource definition in the Helm chart.</p>