<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jason van Brackel on Medium]]></title>
        <description><![CDATA[Stories by Jason van Brackel on Medium]]></description>
        <link>https://medium.com/@jasonvb?source=rss-53c5592f6149------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tAAn35wfYnHuj3mk</url>
            <title>Stories by Jason van Brackel on Medium</title>
            <link>https://medium.com/@jasonvb?source=rss-53c5592f6149------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:02:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jasonvb/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Getting Started with AirGap Deployment of Longhorn Block Storage with Zarf]]></title>
            <link>https://medium.com/defense-unicorns/getting-started-with-airgap-deployment-of-longhorn-block-storage-with-zarf-bdd6edfd65b7?source=rss-53c5592f6149------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdd6edfd65b7</guid>
            <category><![CDATA[longhorns]]></category>
            <category><![CDATA[airgap]]></category>
            <category><![CDATA[backup]]></category>
            <category><![CDATA[zarf]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Jason van Brackel]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 14:17:03 GMT</pubDate>
            <atom:updated>2023-03-20T14:17:03.863Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Longhorn?</h3><p><a href="https://longhorn.io/">Longhorn</a> is a cloud-native block storage project from the Cloud Native Computing Foundation designed to be deployed on Kubernetes clusters. It uses object storage for backups like Amazon S3 or MinIO for non-cloud deployments.</p><p>It provides block storage that is highly available, scalable, and fault-tolerant by distributing the storage across multiple nodes in a Kubernetes cluster and replicating the data across those nodes in Longhorn Volumes.</p><figure><img alt="Architecturual Concepts Diagram of the Longhorn Cloud Storage Platform pulled from https://longhorn.io" src="https://cdn-images-1.medium.com/max/1024/1*CQbSy-EK6QjgdUz3ZDA8sQ.png" /><figcaption>Longhorn High Level Architecture source: <a href="https://longhorn.io/">https://longhorn.io</a></figcaption></figure><p>This ensures that even if a node fails, the data remains available and can be accessed from other nodes. Longhorn also provides backup and restore, snapshotting, and encryption to ensure that data is secure and recoverable.</p><p>“In addition, it supports the creation of Disaster Recovery clusters that can be used to restore data if an entire cluster goes down.</p><p><strong>Note: </strong>This blog post has an associated YouTube video you can find on the <a href="https://www.youtube.com/@defenseunicorns">Defense Unicorns YouTube channel</a>. As these examples evolved over the last month as this was developed, there are slight differences between the video, the screenshots and the code.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fsqbp5NyLJXA&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dsqbp5NyLJXA&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Fsqbp5NyLJXA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5c53dd940af47028ace1a9f903419d76/href">https://medium.com/media/5c53dd940af47028ace1a9f903419d76/href</a></iframe><h3>Environment Setup</h3><p>For this example, we’ll assume no test environment setup, so your milage may vary.</p><h3>Install the Zarf Binary</h3><ul><li><a href="https://zarf.dev/install">Use the Zarf Installation Instructions</a> to install the Zarf binary onto your machine.</li><li>You can check the version with the zarf version command.</li></ul><pre>doug in ~/src/github.com/defenseunicorns 🦄 zarf version<br>v0.24.2</pre><h3>Initialize Zarf</h3><p>You’ll need a Kubernetes cluster. Installing a container runtime like <a href="https://docker.io/">Docker</a>, and setting up a Kubernetes cluster is beyond the scope of this tutorial, but I’ll quickly show you how to create a cluster with <a href="https://k3d.io/">K3d</a>.</p><ul><li><a href="https://k3d.io/v5.4.7/#installation">Use the instructions for your OS to install k3d</a>.</li><li>Create a Kubernetes cluster with k3d.</li></ul><pre>doug in ~/src/github.com/defenseunicorns 🦄 k3d cluster create longhorn-example<br>INFO[0000] Prep: Network<br>INFO[0000] Created network &#39;k3d-longhorn-example&#39;<br>INFO[0000] Created image volume k3d-longhorn-example-images<br>INFO[0000] Starting new tools node...<br>INFO[0000] Starting Node &#39;k3d-longhorn-example-tools&#39;<br>INFO[0001] Creating node &#39;k3d-longhorn-example-server-0&#39;<br>INFO[0001] Creating LoadBalancer &#39;k3d-longhorn-example-serverlb&#39;<br>INFO[0001] Using the k3d-tools node to gather environment information<br>INFO[0001] Starting new tools node...<br>INFO[0001] Starting Node &#39;k3d-longhorn-example-tools&#39;<br>INFO[0002] Starting cluster &#39;longhorn-example&#39;<br>INFO[0002] Starting servers...<br>INFO[0002] Starting Node &#39;k3d-longhorn-example-server-0&#39;<br>INFO[0006] All agents already running.<br>INFO[0006] Starting helpers...<br>INFO[0006] Starting Node &#39;k3d-longhorn-example-serverlb&#39;<br>INFO[0012] Injecting records for hostAliases (incl. host.k3d.internal) and for 3 network members into CoreDNS configmap...<br>INFO[0015] Cluster &#39;longhorn-example&#39; created successfully!<br>INFO[0015] You can now use it like this:<br>kubectl cluster-info</pre><ul><li><strong>Note: </strong>If you get this error, make sure Docker is running.</li></ul><pre>doug in ~/src/github.com/defenseunicorns 🦄 k3d cluster create<br>ERRO[0000] Failed to get nodes for cluster &#39;k3s-default&#39;: docker failed to get containers with labels &#39;map[k3d.cluster:k3s-default]&#39;: failed to list containers: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?<br>INFO[0000] Prep: Network<br>ERRO[0000] Failed Cluster Preparation: Failed Network Preparation: failed to create cluster network: failed to check for duplicate docker networks: docker failed to list networks: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?<br>ERRO[0000] Failed to create cluster &gt;&gt;&gt; Rolling Back<br>INFO[0000] Deleting cluster &#39;k3s-default&#39;<br>ERRO[0000] Failed to get nodes for cluster &#39;k3s-default&#39;: docker failed to get containers with labels &#39;map[k3d.cluster:k3s-default]&#39;: failed to list containers: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?<br>ERRO[0000] failed to get cluster: No nodes found for given cluster<br>FATA[0000] Cluster creation FAILED, also FAILED to rollback changes!</pre><h3>Initialize Zarf</h3><p>Now that you have a Kubernetes cluster, you’re going to initialize Zarf with the zarf init command. It will look different depending on your operating system. Feel free to reject or accept optional components. It’s not essential to our work today.</p><pre>doug in ~/src/github.com/defenseunicorns 🦄 zarf init<br>Saving log file to /var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-11-39-26-2360079011.log<br>         *,<br>         *(((&amp;&amp;&amp;&amp;&amp;/*.<br>          *(((((%&amp;&amp;&amp;&amp;&amp;&amp;&amp;*,<br>           *(((((((&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;*              ,,*****,.                      **%&amp;&amp;&amp;&amp;&amp;((((((<br>            *(((((((((&amp;&amp;&amp;&amp;&amp;&amp;&amp;@*    **@@@@@@&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;@@@@@**         */&amp;&amp;&amp;&amp;&amp;&amp;((((((((((<br>              *((((((///(&amp;&amp;&amp;&amp;&amp;&amp;@@@@&amp;&amp;&amp;&amp;@@@@@@@@@&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;@/* *%&amp;&amp;&amp;&amp;&amp;&amp;/////((((((*<br>                *(((///////&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;@@@@@@@@@&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;(%&amp;&amp;&amp;/**///////(/*<br>       */&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;*/***&amp;%&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;/*******///*<br>   *&amp;%&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;***&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;****/&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;(/*<br> */((((((((((((((///////******%%&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;//&amp;@@*&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;#%&amp;&amp;&amp;&amp;*/####(/////((((/.<br>     */((((((((((///////******%%%%%%%%%(##@@@//%&amp;%%%%%%%&amp;%&amp;%%&amp;&amp;/(@@(/&amp;&amp;(***///////(((*<br>          ***(((((/////********%%%%%%%/&amp;%***/((%%%%%%%%%%%%%%%%(#&amp;@*%/%%***/////**<br>            *&amp;&amp;%%%%%%//*******%%%%%%%%@@****%%/%%%%%%%%%%%%%%%%%%***@@%%**(%%%&amp;&amp;*<br>          *&amp;&amp;%%%%%(////******/(%%%%%%%@@@**@@&amp;%%%%%%%%%%%%%%%%%(@@*%@@%%*****////%&amp;*<br>        *&amp;%%%%%#////////***/////%%%%%%*@@@@@/%%%%%%%%%%%%%%%%%%%%@@@@%%*****///////((*<br>       *%%%%((((///////*    *////(%%%%%%##%%%%%%%%%%%(%%%%*%%%%%%%%%%%*<br>      *(((((((/***            */////#%%%%%%%%%%#%%%%%%%%%%%%%%%%%%%%#*<br>                   %%(           ,*///((%%%%%%%%(**/#%%%##**/%%%%%*<br>                 %%%&amp;&amp;&amp;&amp;           *///*/(((((########//######**<br>                 %&amp;&amp;&amp;&amp;&amp;*          *#######(((((((//////((((*<br>                                  ###%##############(((#####*<br>                   %@&amp;&amp;          *&amp;#(%######*#########(#####/<br>                   /&amp;&amp;* ..       ,&amp;#(/%####(*#########/#####/             #%@%&amp;&amp;&amp;<br>             **         &amp;&amp;     ./%##((*&amp;####/(#######(#####*(*            %&amp;&amp;&amp;&amp;&amp;&amp;<br>           *@%%@*             *&amp;#####((((####*(#####(*###(*(##*              ,  %@&amp;<br>          *@%%%%*            *%######((((*%####/*((*%####/*(###*  *<br>         *@%%%%%%*      *##* **#(###((((///#*#*(((((/#**#((*(##**#,*/##*,    %@&amp;&amp;<br>         *@%%%*%%%*  ****,*##/*#*##(((((((/(((((((((/(((*(((((###########*,  #&amp;&amp;#<br>         *@%%%*(%%%/*   **######(#((..((((((((((((((((((*  ,*(#####(((((*,<br>         *@%%%#(*%%%%*   ,**/####(* */(((((((((((((((((*     ,**,<br>          *@%%%*(/(%%%%/*     ******(((((((((((*(((((*<br>           *@%%%#(((*/%%%%%%##%%*((((((((((((**((((*<br>            *@%%%%*(((((((((((((((((((((((*/%*((*.             (&amp;&amp;&amp;(<br>             ,*%%%%%%*((((((((((((((((**%%%**,                (&amp;<br>                *%%%%%%%%%(/*****(#%%%%%**                      &amp;%<br>                   ,**%%%%%%%%%%%%%***<br>             ,((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((,<br>                         .....(((((((/////////////////((((((((.....<br>            ///////////////      ///////      *****************  ***************,<br>                    ////.       ///  ////     *///          ***  ****<br>                 ////,         ///    ////    *///////////////.  /////**/******<br>              /////          //////////////   *///      *///     ///*<br>           ./////////////// ////         ///  *///        ////   ///*<br><br>It seems the init package could not be found locally, but can be downloaded from<br>https://github.com/defenseunicorns/zarf/releases/download/v0.24.2/zarf-init-arm64-v0.24.2.tar.zst<br>Note: This will require an internet connection.<br>? Do you want to download this init package? Yes<br>  ✔  Downloading https://github.com/defenseunicorns/zarf/releases/download/v0.24.2/zarf-init-arm64-v0.24.2.tar.zst<br>  ✔  Loading Zarf Package /Users/jason/.zarf-cache/zarf-init-arm64-v0.24.2.tar.zst<br>kind: ZarfInitConfig<br>metadata:<br>  name: init<br>  description: Used to establish a new Zarf cluster<br>  architecture: arm64<br>build:<br>  terminal: fv-az363-679<br>  user: runner<br>  architecture: arm64<br>  timestamp: Tue, 14 Feb 2023 02:03:31 +0000<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: zarf-injector<br>  description: |<br>    Bootstraps a Kubernetes cluster by cloning a running pod in the cluster and hosting the registry image.<br>    Removed and destroyed after the Zarf Registry is self-hosting the registry image.<br>  required: true<br>  cosignKeyPath: cosign.pub<br>  files:<br>  - source: sget://defenseunicorns/zarf-injector:arm64-2023-02-09<br>    target: &quot;###ZARF_TEMP###/zarf-injector&quot;<br>    executable: true<br>- name: zarf-seed-registry<br>  description: |<br>    Deploys the Zarf Registry using the registry image provided by the Zarf Injector.<br>  required: true<br>  charts:<br>  - name: docker-registry<br>    releaseName: zarf-docker-registry<br>    version: 1.0.0<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/zarf-registry/registry-values.yaml<br>    - packages/zarf-registry/registry-values-seed.yaml<br>    localPath: packages/zarf-registry/chart<br>- name: zarf-registry<br>  description: |<br>    Updates the Zarf Registry to use the self-hosted registry image.<br>    Serves as the primary docker registry for the cluster.<br>  required: true<br>  charts:<br>  - name: docker-registry<br>    releaseName: zarf-docker-registry<br>    version: 1.0.0<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/zarf-registry/registry-values.yaml<br>    localPath: packages/zarf-registry/chart<br>  manifests:<br>  - name: registry-connect<br>    namespace: zarf<br>    files:<br>    - packages/zarf-registry/connect.yaml<br>  - name: kep-1755-registry-annotation<br>    namespace: zarf<br>    files:<br>    - packages/zarf-registry/configmap.yaml<br>  images:<br>  - registry:2.8.1<br>- name: zarf-agent<br>  description: |<br>    A Kubernetes mutating webhook to enable automated URL rewriting for container<br>    images and git repository references in Kubernetes manifests. This prevents<br>    the need to manually update URLs from their original sources to the Zarf-managed<br>    docker registry and git server.<br>  required: true<br>  actions:<br>    onCreate:<br>      before:<br>      - cmd: make init-package-local-agent AGENT_IMAGE=&quot;agent:v0.24.2&quot;<br>  manifests:<br>  - name: zarf-agent<br>    namespace: zarf<br>    files:<br>    - packages/zarf-agent/manifests/service.yaml<br>    - packages/zarf-agent/manifests/secret.yaml<br>    - packages/zarf-agent/manifests/deployment.yaml<br>    - packages/zarf-agent/manifests/webhook.yaml<br>  images:<br>  - ghcr.io/defenseunicorns/zarf/agent:v0.24.2<br>- name: logging<br>  description: |<br>    Deploys the Promtail Grafana &amp; Loki (PGL) stack.<br>    Aggregates logs from different containers and presents them in a web dashboard.<br>    Recommended if no other logging stack is deployed in the cluster.<br>  charts:<br>  - name: loki-stack<br>    releaseName: zarf-loki-stack<br>    url: https://grafana.github.io/helm-charts<br>    version: 2.8.9<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/logging-pgl/pgl-values.yaml<br>  manifests:<br>  - name: logging-connect<br>    namespace: zarf<br>    files:<br>    - packages/logging-pgl/connect.yaml<br>  images:<br>  - docker.io/grafana/promtail:2.7.0<br>  - grafana/grafana:8.3.5<br>  - grafana/loki:2.6.1<br>  - quay.io/kiwigrid/k8s-sidecar:1.19.2<br>- name: git-server<br>  description: |<br>    Deploys Gitea to provide git repositories for Kubernetes configurations.<br>    Required for GitOps deployments if no other git server is available.<br>  actions:<br>    onDeploy:<br>      after:<br>      - maxTotalSeconds: 60<br>        maxRetries: 3<br>        cmd: ./zarf internal create-read-only-gitea-user<br>  charts:<br>  - name: gitea<br>    releaseName: zarf-gitea<br>    url: https://dl.gitea.io/charts<br>    version: 7.0.2<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/gitea/gitea-values.yaml<br>  manifests:<br>  - name: git-connect<br>    namespace: zarf<br>    files:<br>    - packages/gitea/connect.yaml<br>  images:<br>  - gitea/gitea:1.18.3<br>variables:<br>- name: K3S_ARGS<br>  description: Arguments to pass to K3s<br>  default: --disable traefik<br>- name: REGISTRY_EXISTING_PVC<br>  description: &quot;Optional: Use an existing PVC for the registry instead of creating a new one. If this is set, the REGISTRY_PVC_SIZE variable will be ignored.&quot;<br>- name: REGISTRY_PVC_SIZE<br>  description: The size of the persistent volume claim for the registry<br>  default: 20Gi<br>- name: REGISTRY_CPU_REQ<br>  description: The CPU request for the registry<br>  default: 100m<br>- name: REGISTRY_MEM_REQ<br>  description: The memory request for the registry<br>  default: 256Mi<br>- name: REGISTRY_CPU_LIMIT<br>  description: The CPU limit for the registry<br>  default: &quot;3&quot;<br>- name: REGISTRY_MEM_LIMIT<br>  description: The memory limit for the registry<br>  default: 2Gi<br>- name: REGISTRY_HPA_MIN<br>  description: The minimum number of registry replicas<br>  default: &quot;1&quot;<br>- name: REGISTRY_HPA_MAX<br>  description: The maximum number of registry replicas<br>  default: &quot;5&quot;<br>- name: REGISTRY_HPA_ENABLE<br>  description: Enable the Horizontal Pod Autoscaler for the registry<br>  default: &quot;true&quot;<br>- name: GIT_SERVER_EXISTING_PVC<br>  description: &quot;Optional: Use an existing PVC for the git server instead of creating a new one. If this is set, the GIT_SERVER_PVC_SIZE variable will be ignored.&quot;<br>- name: GIT_SERVER_PVC_SIZE<br>  description: The size of the persistent volume claim for git server<br>  default: 10Gi<br>- name: GIT_SERVER_CPU_REQ<br>  description: The CPU request for git server<br>  default: 200m<br>- name: GIT_SERVER_MEM_REQ<br>  description: The memory request for git server<br>  default: 512Mi<br>- name: GIT_SERVER_CPU_LIMIT<br>  description: The CPU limit for git server<br>  default: &quot;3&quot;<br>- name: GIT_SERVER_MEM_LIMIT<br>  description: The memory limit for git server<br>  default: 2Gi<br>constants:<br>- name: AGENT_IMAGE<br>  value: agent:v0.24.2<br>This package has 9 artifacts with software bill-of-materials (SBOM) included. You can view them now<br>in the zarf-sbom folder in this directory or to go directly to one, open this in your browser:<br>/Users/jason/src/github.com/defenseunicorns/zarf-sbom/sbom-viewer-docker.io_grafana_promtail_2.7.0.html<br>* This directory will be removed after package deployment.<br>? Deploy this Zarf package? Yes<br>───────────────────────────────────────────────────────────────────────────────────────<br>name: logging<br>charts:<br>- name: loki-stack<br>  releaseName: zarf-loki-stack<br>  url: https://grafana.github.io/helm-charts<br>  version: 2.8.9<br>  namespace: zarf<br>  valuesFiles:<br>  - packages/logging-pgl/pgl-values.yaml<br>manifests:<br>- name: logging-connect<br>  namespace: zarf<br>  files:<br>  - packages/logging-pgl/connect.yaml<br>images:<br>- docker.io/grafana/promtail:2.7.0<br>- grafana/grafana:8.3.5<br>- grafana/loki:2.6.1<br>- quay.io/kiwigrid/k8s-sidecar:1.19.2<br>Deploys the Promtail Grafana &amp; Loki (PGL) stack. Aggregates logs from different containers and<br>presents them in a web dashboard. Recommended if no other logging stack is deployed in the cluster.<br>? Deploy the logging component? No<br>───────────────────────────────────────────────────────────────────────────────────────<br>name: git-server<br>actions:<br>  onDeploy:<br>    after:<br>    - maxTotalSeconds: 60<br>      maxRetries: 3<br>      cmd: ./zarf internal create-read-only-gitea-user<br>charts:<br>- name: gitea<br>  releaseName: zarf-gitea<br>  url: https://dl.gitea.io/charts<br>  version: 7.0.2<br>  namespace: zarf<br>  valuesFiles:<br>  - packages/gitea/gitea-values.yaml<br>manifests:<br>- name: git-connect<br>  namespace: zarf<br>  files:<br>  - packages/gitea/connect.yaml<br>images:<br>- gitea/gitea:1.18.3<br>Deploys Gitea to provide git repositories for Kubernetes configurations. Required for GitOps<br>deployments if no other git server is available.<br>? Deploy the git-server component? No<br><br>  📦 ZARF-INJECTOR COMPONENT<br><br>✔  Copying 1 files<br>  ✔  Gathering cluster information<br>  ⠋  Attempting to bootstrap with the [k3d-longhorn-example-server-0]/rancher/mirrored-library-tr  ⠙  Attempting to bootstrap with the [k3d-longhorn-example-server-0]/rancher/mirrored-library-tr  ⠹  Attempting to bootstrap with the [k3d-longhorn-example-server-0]/rancher/mirrored-library-tr  ⠸  Attempting to bootstrap with the [k3d-longhorn-example-server-0]/rancher/mirrored-library-tr  ⠼  Attempting to bootstrap with the [k3d-longhorn-example-server-0]/rancher/mirrored-library-tr  ⠴  Attempting to bootstrap with the [k3d-longhorn-example-server-0]/rancher/mirrored-library-tr  ✔  Attempting to bootstrap the seed image into the cluster<br>  📦 ZARF-SEED-REGISTRY COMPONENT<br><br>  ✔  Loading the Zarf State from the Kubernetes cluster<br>  ✔  Processing helm chart docker-registry:1.0.0 from Zarf-generated helm chart<br><br>  📦 ZARF-REGISTRY COMPONENT<br><br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:61003/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Processing helm chart docker-registry:1.0.0 from Zarf-generated helm chart<br>  ✔  Starting helm chart generation registry-connect<br>  ⠋  Processing helm chart raw-init-zarf-registry-registry-connect:0.1.1677170366 from Zarf-generat  ✔  Processing helm chart raw-init-zarf-registry-registry-connect:0.1.1677170366 from Zarf-generated helm chart<br>  ✔  Starting helm chart generation kep-1755-registry-annotation<br>  ⠋  Processing helm chart raw-init-zarf-registry-kep-1755-registry-annotation:0.1.1677170366 from   ✔  Processing helm chart raw-init-zarf-registry-kep-1755-registry-annotation:0.1.1677170366 from Zarf-generated helm chart<br><br>  📦 ZARF-AGENT COMPONENT<br><br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:61015/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Starting helm chart generation zarf-agent<br>  ⠋  Processing helm chart raw-init-zarf-agent-zarf-agent:0.1.1677170366 from Zarf-generated helm c  ✔  Processing helm chart raw-init-zarf-agent-zarf-agent:0.1.1677170366 from Zarf-generated helm chart<br>  ✔  Zarf deployment complete<br><br>     Application | Username  | Password                 | Connect<br>     Registry    | zarf-push | QFFiAMQ4GBW6BJ01fc4czE2W | zarf connect registry<br>doug in ~/src/github.com/defenseunicorns 🦄</pre><h3>Longhorn Prerequisites</h3><p>Longhorn takes advantage of a number of technologies like <a href="https://longhorn.io/docs/1.4.0/deploy/install/#installing-nfsv4-client">NFS</a> and <a href="https://longhorn.io/docs/1.4.0/deploy/install/#installing-open-iscsi">Open-ISCSI</a>. Make sure these are installed as the <a href="https://github.com/defenseunicorns/zarf/tree/main/examples/longhorn">Longhorn Zarf Package</a> includes a <a href="https://github.com/JasonvanBrackel/zarf/blob/main/examples/longhorn/zarf.yaml#L9">built-in check</a> for Longhorn Pre-requisites as spelled out in the <a href="https://longhorn.io/docs/1.4.0/deploy/install/#using-the-environment-check-script">Longhorn documentation</a>. If these are not installed the Zarf package deployment will fail. The <a href="https://longhorn.io/docs/1.4.0/deploy/install/#installation-requirements">Installation Requirements</a> documentation catalogs these.</p><h3>Getting The Longhorn Zarf Example</h3><p>To create the Zarf Longhorn Package, you can start with the <a href="https://docs.zarf.dev/examples/longhorn/">Zarf Longhorn Example</a>.</p><ul><li>Navigate to the <a href="https://github.com/defenseunicorns/zarf">Zarf repository</a>.</li><li>Press the Code button and copy the https URL.</li></ul><figure><img alt="Screenshot of the Code drop down button with the HTTPS tab open." src="https://cdn-images-1.medium.com/max/836/1*PMH2AWilp7hk4zrS2cotUA.png" /></figure><ul><li>Clone the git repository in your favorite terminal</li></ul><pre>doug in ~ 🦄 git clone https://github.com/defenseunicorns/zarf.git<br>Cloning into &#39;zarf&#39;...<br>remote: Enumerating objects: 16346, done.<br>remote: Counting objects: 100% (846/846), done.<br>remote: Compressing objects: 100% (388/388), done.<br>remote: Total 16346 (delta 515), reused 741 (delta 450), pack-reused 15500<br>Receiving objects: 100% (16346/16346), 37.57 MiB | 7.04 MiB/s, done.<br>Resolving deltas: 100% (10796/10796), done.</pre><ul><li>Navigate to the examples folder.</li></ul><pre>doug in ~ 🦄 cd zarf/examples/longhorn<br>doug in ~/zarf/examples/longhorn on main 🦄</pre><h3>Longhorn Zarf Files</h3><ul><li>Let’s examine the Zarf Package Files. We’ll discuss each file one at a time.</li></ul><h3>README.md</h3><p>The Readme.md file is used to populate the Example in the Zarf documentation. It also populates the UI on the github.com folder for that directory.</p><h3>values.yaml</h3><p>The values.yaml file is the <a href="https://longhorn.io/docs/1.4.0/advanced-resources/deploy/customizing-default-settings/#using-helm">default values file for Longhorn</a>, with <a href="https://longhorn.io/docs/1.4.0/advanced-resources/os-distro-specific/csi-on-k3s/">modifications required to support K3s</a>. Modify this for your needs.</p><h3>connect.yaml</h3><p>This file creates a service for the longhorn-ui, so an operator can connect to it with the <a href="https://docs.zarf.dev/docs/user-guide/the-zarf-cli/cli-commands/zarf_connect">zarf connect command</a>. This creates a <a href="https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/">kubernetes port-forward</a> to the service.</p><p>Any service with the zarf.dev/connect-name label can be accessed using Zarf. The zarf.dev/connect-description annotation is used to populate the output of the <a href="https://docs.zarf.dev/docs/user-guide/the-zarf-cli/cli-commands/zarf_connect_list">zarf connect list command</a>.</p><p>In addition to this label and annotation, Zarf also supports the zarf.dev/connect-url annotation. This URL is the initial URL that will be opened in the web browser when the operator runs the zarf connect command. You can see examples of this in the <a href="https://github.com/defenseunicorns/zarf/blob/main/examples/dos-games/manifests/service.yaml#L8">dos-games example</a> and in the <a href="https://github.com/defenseunicorns/zarf/blob/main/packages/zarf-registry/connect.yaml#L10">docker registry included</a> in the ZarfInitPackage.</p><h3>zarf.yaml</h3><p>This is ZarfPackageConfig for the Longhorn Example. Let’s explore each section of this manifest’s components.</p><figure><img alt="Screenshot of the zarf.yaml file lines concerned with the Longhorn environment check" src="https://cdn-images-1.medium.com/max/1024/1*cQMy5v4ui-Ma6xVXSfddJQ.png" /></figure><p>This is the Longhorn environment check, used to check the nodes and ensure they have installed the Longhorn prerequisites.</p><figure><img alt="Screenshot of the zarf.yaml file lines concerned with the the onDeploy, before action and the onRemove, before action. These ensure that the environment is checked for Longhorn prerequisites, and that a prerequisite kubectl command is run, so Longhorn can be removed when requested." src="https://cdn-images-1.medium.com/max/1024/1*5NpgPFAFS2UpzjEpeOL63A.png" /></figure><p>These actions are onDeploy and onRemove. <a href="https://docs.zarf.dev/docs/user-guide/component-actions">Zarf supports actions for different events</a>. In this example, the onDeploy &gt; before action is running the environmental check. The onRemove &gt; before action runs a kubectl <a href="https://longhorn.io/docs/1.4.0/deploy/uninstall/#prerequisite">command that allows the operator to remove Longhorn</a>. It’s a safety precaution, so you don’t remove data unintentionally. If you don’t have backups and do a Zarf remove, your data and replicas will be irreversibly gone.</p><figure><img alt="Screenshot of the zarf.yaml file lines concerned with files included in the package. jq is a prerequisite of the environment check and must be included with the package." src="https://cdn-images-1.medium.com/max/1024/1*C7I6HlZf5p5Q3gKccG2ZVg.png" /></figure><p><a href="https://stedolan.github.io/jq/">jq</a> is a JSON command line parser used by the Longhorn environment check. It is installed on most Linux systems, but we can’t assume that, so we include it in the package.</p><figure><img alt="Screenshot of the zarf.yaml file lines concerned with the Kubenetes manifest for the zarf connect component of the service." src="https://cdn-images-1.medium.com/max/1024/1*7v8jg8l0LcW7CBn1VHb8vw.png" /></figure><p>These lines are concerned with the aforementioned connect.yaml Kubernetes service manifest.</p><figure><img alt="Screenshot of the zarf.yaml file lines concerned with the Longhorn helm chart and the associated Longhorn helm values file." src="https://cdn-images-1.medium.com/max/1024/1*Hpwybrs0JMkgzhrmD2NU-w.png" /></figure><p>When deploying the chart with Zarf, these lines will pull the Helm chart from the Longhorn Helm repository and apply the aforementioned local values.yaml file.</p><figure><img alt="Screenshot of the zarf.yaml file lines concerned with the container images required to install Longhorn in an air gapped environment." src="https://cdn-images-1.medium.com/max/1024/1*WPLjcWKDuaj64THIVXi8zw.png" /></figure><p>These are the images required to <a href="https://longhorn.io/docs/1.4.0/advanced-resources/deploy/airgap/">deploy and run Longhorn in an air gapped environment</a>.</p><h3>Creating the Zarf Package</h3><ul><li>Run the zarf package create command in the Longhorn directory.</li></ul><pre>doug in ~/zarf/examples/longhorn on main 🦄 zarf package create .<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-03-03-11-23-49-1243511006.log<br><br>Using build directory .<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: longhorn-example<br>  description: Example package for Longhorn cloud native distributed block storage for Kubernetes<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Fri, 03 Mar 2023 11:23:49 -0500<br>  version: v0.24.2-6-g22e84ab<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: longhorn-environment-check<br>  required: true<br>  files:<br>  - source: https://raw.githubusercontent.com/longhorn/longhorn/v1.4.0/scripts/environment_check.sh<br>    target: environment_check.sh<br>    executable: true<br>- name: longhorn<br>  description: Deploy Longhorn into a Kubernetes cluster.  https://longhorn.io<br>  required: true<br>  actions:<br>    onDeploy:<br>      before:<br>      - env:<br>        - PATH=$PATH:./<br>      - cmd: alias kubectl=&quot;zarf tools kubectl&quot;<br>      - cmd: ./environment_check.sh<br>    onRemove:<br>      before:<br>      - env:<br>        - PATH=$PATH:./<br>      - cmd: alias kubectl=&quot;zarf tools kubectl&quot;<br>      - cmd: &quot;kubectl -n longhorn-system patch -p &#39;{\&quot;value\&quot;: \&quot;true\&quot;}&#39; --type=merge lhs deleting-confirmation-flag&quot;<br>  files:<br>  - source: https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64<br>    target: jq<br>    executable: true<br>  charts:<br>  - name: longhorn<br>    url: https://charts.longhorn.io<br>    version: 1.4.0<br>    namespace: longhorn-system<br>    valuesFiles:<br>    - values.yaml<br>  manifests:<br>  - name: longhorn-connect<br>    namespace: longhorn-system<br>    files:<br>    - connect.yaml<br>  images:<br>  - longhornio/csi-attacher:v3.4.0<br>  - longhornio/csi-provisioner:v2.1.2<br>  - longhornio/csi-resizer:v1.3.0<br>  - longhornio/csi-snapshotter:v5.0.1<br>  - longhornio/csi-node-driver-registrar:v2.5.0<br>  - longhornio/livenessprobe:v2.8.0<br>  - longhornio/backing-image-manager:v1.4.0<br>  - longhornio/longhorn-engine:v1.4.0<br>  - longhornio/longhorn-instance-manager:v1.4.0<br>  - longhornio/longhorn-manager:v1.4.0<br>  - longhornio/longhorn-share-manager:v1.4.0<br>  - longhornio/longhorn-ui:v1.4.0<br>  - longhornio/support-bundle-kit:v0.0.17<br>? Create this Zarf package? Yes<br><br>Specify a maximum file size for this package in Megabytes. Above this size, the package will be<br>split into multiple files. 0 will disable this feature.<br>? Please provide a value for &quot;Maximum Package Size&quot; 0<br><br><br>  📦 LONGHORN-ENVIRONMENT-CHECK COMPONENT<br><br><br>  ✔  Downloading https://raw.githubusercontent.com/longhorn/longhorn/v1.4.0/scripts/environment_check.sh<br><br><br>  📦 LONGHORN COMPONENT<br><br><br>  ✔  Processing helm chart longhorn:1.4.0 from repo https://charts.longhorn.io<br>  ✔  Downloading https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64<br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 COMPONENT IMAGES<br><br><br>  ✔  Loading metadata for 13 images. This step may take several seconds to complete.<br>  ✔  Pulling 13 images (786.80 MBs)<br>  ✔  Creating SBOMs for 13 images and 2 components with files.</pre><h3>Deploying the Zarf Package</h3><ul><li>You can deploy the Longhorn Package with the zarf package deploy command.</li></ul><pre>doug in ~/zarf/examples/longhorn on main 🦄 zarf package deploy<br><br>Saving log file to /tmp/zarf-2023-03-03-19-57-43-1761103531.log<br>  ✔  Loading Zarf Package zarf-package-longhorn-example-amd64.tar.zst<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: longhorn-example<br>  description: Example package for Longhorn cloud native distributed block storage for Kubernetes<br>  architecture: amd64<br>build:<br>  terminal: k3s80controller1<br>  user: kuber<br>  architecture: amd64<br>  timestamp: Fri, 03 Mar 2023 19:51:41 +0000<br>  version: v0.24.3<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: longhorn-environment-check<br>  required: true<br>  files:<br>  - source: https://raw.githubusercontent.com/longhorn/longhorn/v1.4.0/scripts/environment_check.sh<br>    target: environment_check.sh<br>    executable: true<br>- name: longhorn<br>  description: Deploy Longhorn into a Kubernetes cluster.  https://longhorn.io<br>  required: true<br>  actions:<br>    onDeploy:<br>      before:<br>      - env:<br>        - PATH=$PATH:./<br>      - cmd: alias kubectl=&quot;zarf tools kubectl&quot;<br>      - cmd: ./environment_check.sh<br>    onRemove:<br>      before:<br>      - env:<br>        - PATH=$PATH:./<br>      - cmd: alias kubectl=&quot;zarf tools kubectl&quot;<br>      - cmd: &quot;kubectl -n longhorn-system patch -p &#39;{\&quot;value\&quot;: \&quot;true\&quot;}&#39; --type=merge lhs deleting-confirmation-flag&quot;<br>  files:<br>  - source: https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64<br>    target: jq<br>    executable: true<br>  charts:<br>  - name: longhorn<br>    url: https://charts.longhorn.io<br>    version: 1.4.0<br>    namespace: longhorn-system<br>    valuesFiles:<br>    - values.yaml<br>  manifests:<br>  - name: longhorn-connect<br>    namespace: longhorn-system<br>    files:<br>    - connect.yaml<br>  images:<br>  - longhornio/csi-attacher:v3.4.0<br>  - longhornio/csi-provisioner:v2.1.2<br>  - longhornio/csi-resizer:v1.3.0<br>  - longhornio/csi-snapshotter:v5.0.1<br>  - longhornio/csi-node-driver-registrar:v2.5.0<br>  - longhornio/livenessprobe:v2.8.0<br>  - longhornio/backing-image-manager:v1.4.0<br>  - longhornio/longhorn-engine:v1.4.0<br>  - longhornio/longhorn-instance-manager:v1.4.0<br>  - longhornio/longhorn-manager:v1.4.0<br>  - longhornio/longhorn-share-manager:v1.4.0<br>  - longhornio/longhorn-ui:v1.4.0<br>  - longhornio/support-bundle-kit:v0.0.17<br>This package has 15 artifacts with software bill-of-materials (SBOM) included. You can view them now<br>in the zarf-sbom folder in this directory or to go directly to one, open this in your browser:<br>/home/kuber/zarf/examples/longhorn/zarf-sbom/sbom-viewer-longhornio_backing-image-manager_v1.4.0.html<br><br>* This directory will be removed after package deployment.<br><br>? Deploy this Zarf package? Yes<br><br><br>  📦 LONGHORN-ENVIRONMENT-CHECK COMPONENT<br><br><br>  ✔  Copying 1 files<br><br><br>  📦 LONGHORN COMPONENT<br><br><br>  ✔  Completed &quot;&quot;<br>  ✔  Completed &quot;alias kubectl=&quot;zarf tools kubectl&quot;&quot;<br>     [INFO]  Required dependencies &#39;kubectl jq mktemp&#39; are installed.<br>     [INFO]  Hostname uniqueness check is passed.<br>     [INFO]  Waiting for longhorn-environment-check pods to become ready (0/2)...<br>     [INFO]  All longhorn-environment-check pods are ready (2/2).<br>     [WARN]  Unable to check kernel config CONFIG_NFS_V4_1 on node k3s80controller1<br>     [WARN]  Unable to check kernel config CONFIG_NFS_V4_1 on node k3s80worker0<br>     [WARN]  Unable to check kernel config CONFIG_NFS_V4_2 on node k3s80controller1<br>     [WARN]  Unable to check kernel config CONFIG_NFS_V4_2 on node k3s80worker0<br>     [WARN]  NFS client kernel support, CONFIG_NFS_V4_1 CONFIG_NFS_V4_2, is not enabled on Longhorn nodes. Please refer to https://longhorn.io/docs/1.4.0/deploy/install/#installing-nfsv4-client for more information.<br>     [INFO]  Required packages are installed.<br>     [INFO]  MountPropagation is enabled.<br>     [INFO]  Cleaning up longhorn-environment-check pods...<br>     [INFO]  Cleanup completed.<br>  ✔  Completed &quot;./environment_check.sh&quot;<br>  ✔  Copying 1 files<br>  ✔  Loading the Zarf State from the Kubernetes cluster<br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:43401/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Processing helm chart longhorn:1.4.0 from https://charts.longhorn.io<br>  ✔  Starting helm chart generation longhorn-connect<br>  ✔  Processing helm chart raw-longhorn-example-longhorn-longhorn-connect:0.1.1677873463 from Zarf-generated helm chart<br>  ✔  Zarf deployment complete<br><br>     Connect Command          | Description<br>     zarf connect longhorn-ui | Connect to the Longhorn User Interface</pre><h3>Using Zarf Connect to Confirm Everything is Working</h3><ul><li>Run the zarf connect command to make sure everything is installed properly.</li></ul><pre>doug in ~/zarf/examples/longhorn on main 🦄 zarf connect longhorn-ui<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-03-03-15-29-23-1248805990.log<br>  ⠋  Looking for a Zarf Connect Label in the cluster (0s)<br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:58961<br>http://127.0.0.1:58961</pre><figure><img alt="Screenshot of the Longhorn frontend user interface." src="https://cdn-images-1.medium.com/max/1024/1*Newnud1c-qpvliC96LqewQ.png" /></figure><p>This should open your web browser displaying the Longhorn front end user interface.</p><h3>Connect with Us</h3><p>If you have any questions about this or run into any issues, please feel free to reach out to us in the #Zarf channel in <a href="https://slack.kubernetes.io/">Kubernetes Slack</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdd6edfd65b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-unicorns/getting-started-with-airgap-deployment-of-longhorn-block-storage-with-zarf-bdd6edfd65b7">Getting Started with AirGap Deployment of Longhorn Block Storage with Zarf</a> was originally published in <a href="https://medium.com/defense-unicorns">Defense Unicorns</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build an Air Gap Mattermost Deployment Package with Zarf]]></title>
            <link>https://medium.com/defense-unicorns/build-an-air-gap-mattermost-deployment-package-with-zarf-638c9a306c75?source=rss-53c5592f6149------2</link>
            <guid isPermaLink="false">https://medium.com/p/638c9a306c75</guid>
            <category><![CDATA[zarf]]></category>
            <category><![CDATA[technical-collaboration]]></category>
            <category><![CDATA[mattermost]]></category>
            <category><![CDATA[airgap]]></category>
            <category><![CDATA[deployment]]></category>
            <dc:creator><![CDATA[Jason van Brackel]]></dc:creator>
            <pubDate>Tue, 07 Mar 2023 14:52:04 GMT</pubDate>
            <atom:updated>2023-03-07T14:52:04.753Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In secure and disconnected environments, the open-source project Mattermost is an excellent collaboration technology that allows technical teams to seamlessly collaborate on distributed teams. The features in Mattermost parallel competing connected Software as a Service (SaaS) offerings like Slack and Microsoft Teams.</p><p>In this blog, you will learn step-by-step how to Package and Deploy a running Mattermost instance with Zarf. This is not a deep dive into long-term air gap planning with Mattermost, but an introduction and a getting started with components required to run Mattermost in an air-gapped environment.</p><p>This blog has a companion video you can follow along with on YouTube.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxxWf-Cwt_9k%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxxWf-Cwt_9k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxxWf-Cwt_9k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0914bf8f85763b13fe8c7346ed2bcd4d/href">https://medium.com/media/0914bf8f85763b13fe8c7346ed2bcd4d/href</a></iframe><h3>Install the Zarf Binary</h3><ul><li><a href="https://zarf.dev/install">Use the Zarf Installation Instructions</a> to install the Zarf binary onto your machine.</li><li>You can check the version with the zarf version command.</li></ul><pre>doug in ~/src/github.com/defenseunicorns 🦄 zarf version<br>v0.24.2</pre><h3>Clone the Zarf Repository</h3><p>We’ll be using the Zarf examples in the source code for some of the components to set up Mattermost.</p><ul><li>Navigate to <a href="https://github.com/defenseunicorns/zarf">https://github.com/defenseunicorns/zarf</a></li><li>Press the &lt; &gt; Code button</li></ul><figure><img alt="Screenshot of the Clone menu in github with the URL for the zarf repository." src="https://cdn-images-1.medium.com/max/413/1*I0s8qFrP7kAtwI8YawUikQ.png" /></figure><ul><li>Copy the HTTPS url.</li><li>Open your favorite terminal and use git to clone the repository.</li></ul><pre>doug in ~ 🦄<br>doug in ~ 🦄 mkdir -p src/github.com/defenseunicorns<br>doug in ~ 🦄 cd src/github.com/defenseunicorns<br>doug in ~/src/github.com/defenseunicorns 🦄 git clone https://github.com/defenseunicorns/zarf.git<br>Cloning into &#39;zarf&#39;...<br>remote: Enumerating objects: 15495, done.<br>remote: Counting objects: 100% (1594/1594), done.<br>remote: Compressing objects: 100% (626/626), done.<br>remote: Total 15495 (delta 1092), reused 1395 (delta 944), pack-reused 13901<br>Receiving objects: 100% (15495/15495), 37.56 MiB | 14.04 MiB/s, done.<br>Resolving deltas: 100% (10123/10123), done.</pre><h3>Initialize Zarf</h3><p>You’ll need a Kubernetes cluster. Installing a container runtime like <a href="https://docker.io/">Docker</a> and setting up a Kubernetes cluster is beyond the scope of this tutorial. But I’ll quickly show you how to create a cluster with <a href="https://k3d.io/">K3d</a>.</p><ul><li><a href="https://k3d.io/v5.4.7/#installation">Use the instructions for your OS to install k3d</a>.</li><li>Create a Kubernetes cluster with k3d.</li></ul><pre>doug in ~/src/github.com/defenseunicorns 🦄 k3d cluster create mattermost-example<br>INFO[0000] Prep: Network<br>INFO[0000] Created network &#39;k3d-mattermost-example&#39;<br>INFO[0000] Created image volume k3d-mattermost-example-images<br>INFO[0000] Starting new tools node...<br>INFO[0000] Starting Node &#39;k3d-mattermost-example-tools&#39;<br>INFO[0001] Creating node &#39;k3d-mattermost-example-server-0&#39;<br>INFO[0001] Creating LoadBalancer &#39;k3d-mattermost-example-serverlb&#39;<br>INFO[0001] Using the k3d-tools node to gather environment information<br>INFO[0001] Starting new tools node...<br>INFO[0001] Starting Node &#39;k3d-mattermost-example-tools&#39;<br>INFO[0002] Starting cluster &#39;mattermost-example&#39;<br>INFO[0002] Starting servers...<br>INFO[0002] Starting Node &#39;k3d-mattermost-example-server-0&#39;<br>INFO[0006] All agents already running.<br>INFO[0006] Starting helpers...<br>INFO[0006] Starting Node &#39;k3d-mattermost-example-serverlb&#39;<br>INFO[0012] Injecting records for hostAliases (incl. host.k3d.internal) and for 3 network members into CoreDNS configmap...<br>INFO[0015] Cluster &#39;mattermost-example&#39; created successfully!<br>INFO[0015] You can now use it like this:<br>kubectl cluster-info</pre><ul><li><strong>Note: </strong>If you get this error, make sure Docker is running.</li></ul><pre>doug in ~/src/github.com/defenseunicorns 🦄 k3d cluster create<br>ERRO[0000] Failed to get nodes for cluster &#39;k3s-default&#39;: docker failed to get containers with labels &#39;map[k3d.cluster:k3s-default]&#39;: failed to list containers: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?<br>INFO[0000] Prep: Network<br>ERRO[0000] Failed Cluster Preparation: Failed Network Preparation: failed to create cluster network: failed to check for duplicate docker networks: docker failed to list networks: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?<br>ERRO[0000] Failed to create cluster &gt;&gt;&gt; Rolling Back<br>INFO[0000] Deleting cluster &#39;k3s-default&#39;<br>ERRO[0000] Failed to get nodes for cluster &#39;k3s-default&#39;: docker failed to get containers with labels &#39;map[k3d.cluster:k3s-default]&#39;: failed to list containers: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?<br>ERRO[0000] failed to get cluster: No nodes found for given cluster<br>FATA[0000] Cluster creation FAILED, also FAILED to rollback changes!</pre><h3>Initialize Zarf</h3><p>You now have a Kubernetes cluster. You’re going to initialize Zarf with the zarf init command. It will look different depending on your operating system. Feel free to reject or take optional components. It’s not important to our work today.</p><pre>doug in ~/src/github.com/defenseunicorns 🦄 zarf init<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-11-39-26-2360079011.log<br><br>         *,<br>         *(((&amp;&amp;&amp;&amp;&amp;/*.<br>          *(((((%&amp;&amp;&amp;&amp;&amp;&amp;&amp;*,<br>           *(((((((&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;*              ,,*****,.                      **%&amp;&amp;&amp;&amp;&amp;((((((<br>            *(((((((((&amp;&amp;&amp;&amp;&amp;&amp;&amp;@*    **@@@@@@&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;@@@@@**         */&amp;&amp;&amp;&amp;&amp;&amp;((((((((((<br>              *((((((///(&amp;&amp;&amp;&amp;&amp;&amp;@@@@&amp;&amp;&amp;&amp;@@@@@@@@@&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;@/* *%&amp;&amp;&amp;&amp;&amp;&amp;/////((((((*<br>                *(((///////&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;@@@@@@@@@&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;(%&amp;&amp;&amp;/**///////(/*<br>       */&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;*/***&amp;%&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;/*******///*<br>   *&amp;%&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;***&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;****/&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;(/*<br> */((((((((((((((///////******%%&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;//&amp;@@*&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;&amp;#%&amp;&amp;&amp;&amp;*/####(/////((((/.<br>     */((((((((((///////******%%%%%%%%%(##@@@//%&amp;%%%%%%%&amp;%&amp;%%&amp;&amp;/(@@(/&amp;&amp;(***///////(((*<br>          ***(((((/////********%%%%%%%/&amp;%***/((%%%%%%%%%%%%%%%%(#&amp;@*%/%%***/////**<br>            *&amp;&amp;%%%%%%//*******%%%%%%%%@@****%%/%%%%%%%%%%%%%%%%%%***@@%%**(%%%&amp;&amp;*<br>          *&amp;&amp;%%%%%(////******/(%%%%%%%@@@**@@&amp;%%%%%%%%%%%%%%%%%(@@*%@@%%*****////%&amp;*<br>        *&amp;%%%%%#////////***/////%%%%%%*@@@@@/%%%%%%%%%%%%%%%%%%%%@@@@%%*****///////((*<br>       *%%%%((((///////*    *////(%%%%%%##%%%%%%%%%%%(%%%%*%%%%%%%%%%%*<br>      *(((((((/***            */////#%%%%%%%%%%#%%%%%%%%%%%%%%%%%%%%#*<br>                   %%(           ,*///((%%%%%%%%(**/#%%%##**/%%%%%*<br>                 %%%&amp;&amp;&amp;&amp;           *///*/(((((########//######**<br>                 %&amp;&amp;&amp;&amp;&amp;*          *#######(((((((//////((((*<br>                                  ###%##############(((#####*<br>                   %@&amp;&amp;          *&amp;#(%######*#########(#####/<br>                   /&amp;&amp;* ..       ,&amp;#(/%####(*#########/#####/             #%@%&amp;&amp;&amp;<br>             **         &amp;&amp;     ./%##((*&amp;####/(#######(#####*(*            %&amp;&amp;&amp;&amp;&amp;&amp;<br>           *@%%@*             *&amp;#####((((####*(#####(*###(*(##*              ,  %@&amp;<br>          *@%%%%*            *%######((((*%####/*((*%####/*(###*  *<br>         *@%%%%%%*      *##* **#(###((((///#*#*(((((/#**#((*(##**#,*/##*,    %@&amp;&amp;<br>         *@%%%*%%%*  ****,*##/*#*##(((((((/(((((((((/(((*(((((###########*,  #&amp;&amp;#<br>         *@%%%*(%%%/*   **######(#((..((((((((((((((((((*  ,*(#####(((((*,<br>         *@%%%#(*%%%%*   ,**/####(* */(((((((((((((((((*     ,**,<br>          *@%%%*(/(%%%%/*     ******(((((((((((*(((((*<br>           *@%%%#(((*/%%%%%%##%%*((((((((((((**((((*<br>            *@%%%%*(((((((((((((((((((((((*/%*((*.             (&amp;&amp;&amp;(<br>             ,*%%%%%%*((((((((((((((((**%%%**,                (&amp;<br>                *%%%%%%%%%(/*****(#%%%%%**                      &amp;%<br>                   ,**%%%%%%%%%%%%%***<br><br>             ,((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((,<br>                         .....(((((((/////////////////((((((((.....<br><br>            ///////////////      ///////      *****************  ***************,<br>                    ////.       ///  ////     *///          ***  ****<br>                 ////,         ///    ////    *///////////////.  /////**/******<br>              /////          //////////////   *///      *///     ///*<br>           ./////////////// ////         ///  *///        ////   ///*<br><br><br><br><br>It seems the init package could not be found locally, but can be downloaded from<br>https://github.com/defenseunicorns/zarf/releases/download/v0.24.2/zarf-init-arm64-v0.24.2.tar.zst<br><br>Note: This will require an internet connection.<br>? Do you want to download this init package? Yes<br>  ✔  Downloading https://github.com/defenseunicorns/zarf/releases/download/v0.24.2/zarf-init-arm64-v0.24.2.tar.zst<br>  ✔  Loading Zarf Package /Users/jason/.zarf-cache/zarf-init-arm64-v0.24.2.tar.zst<br><br>kind: ZarfInitConfig<br>metadata:<br>  name: init<br>  description: Used to establish a new Zarf cluster<br>  architecture: arm64<br>build:<br>  terminal: fv-az363-679<br>  user: runner<br>  architecture: arm64<br>  timestamp: Tue, 14 Feb 2023 02:03:31 +0000<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: zarf-injector<br>  description: |<br>    Bootstraps a Kubernetes cluster by cloning a running pod in the cluster and hosting the registry image.<br>    Removed and destroyed after the Zarf Registry is self-hosting the registry image.<br>  required: true<br>  cosignKeyPath: cosign.pub<br>  files:<br>  - source: sget://defenseunicorns/zarf-injector:arm64-2023-02-09<br>    target: &quot;###ZARF_TEMP###/zarf-injector&quot;<br>    executable: true<br>- name: zarf-seed-registry<br>  description: |<br>    Deploys the Zarf Registry using the registry image provided by the Zarf Injector.<br>  required: true<br>  charts:<br>  - name: docker-registry<br>    releaseName: zarf-docker-registry<br>    version: 1.0.0<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/zarf-registry/registry-values.yaml<br>    - packages/zarf-registry/registry-values-seed.yaml<br>    localPath: packages/zarf-registry/chart<br>- name: zarf-registry<br>  description: |<br>    Updates the Zarf Registry to use the self-hosted registry image.<br>    Serves as the primary docker registry for the cluster.<br>  required: true<br>  charts:<br>  - name: docker-registry<br>    releaseName: zarf-docker-registry<br>    version: 1.0.0<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/zarf-registry/registry-values.yaml<br>    localPath: packages/zarf-registry/chart<br>  manifests:<br>  - name: registry-connect<br>    namespace: zarf<br>    files:<br>    - packages/zarf-registry/connect.yaml<br>  - name: kep-1755-registry-annotation<br>    namespace: zarf<br>    files:<br>    - packages/zarf-registry/configmap.yaml<br>  images:<br>  - registry:2.8.1<br>- name: zarf-agent<br>  description: |<br>    A Kubernetes mutating webhook to enable automated URL rewriting for container<br>    images and git repository references in Kubernetes manifests. This prevents<br>    the need to manually update URLs from their original sources to the Zarf-managed<br>    docker registry and git server.<br>  required: true<br>  actions:<br>    onCreate:<br>      before:<br>      - cmd: make init-package-local-agent AGENT_IMAGE=&quot;agent:v0.24.2&quot;<br>  manifests:<br>  - name: zarf-agent<br>    namespace: zarf<br>    files:<br>    - packages/zarf-agent/manifests/service.yaml<br>    - packages/zarf-agent/manifests/secret.yaml<br>    - packages/zarf-agent/manifests/deployment.yaml<br>    - packages/zarf-agent/manifests/webhook.yaml<br>  images:<br>  - ghcr.io/defenseunicorns/zarf/agent:v0.24.2<br>- name: logging<br>  description: |<br>    Deploys the Promtail Grafana &amp; Loki (PGL) stack.<br>    Aggregates logs from different containers and presents them in a web dashboard.<br>    Recommended if no other logging stack is deployed in the cluster.<br>  charts:<br>  - name: loki-stack<br>    releaseName: zarf-loki-stack<br>    url: https://grafana.github.io/helm-charts<br>    version: 2.8.9<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/logging-pgl/pgl-values.yaml<br>  manifests:<br>  - name: logging-connect<br>    namespace: zarf<br>    files:<br>    - packages/logging-pgl/connect.yaml<br>  images:<br>  - docker.io/grafana/promtail:2.7.0<br>  - grafana/grafana:8.3.5<br>  - grafana/loki:2.6.1<br>  - quay.io/kiwigrid/k8s-sidecar:1.19.2<br>- name: git-server<br>  description: |<br>    Deploys Gitea to provide git repositories for Kubernetes configurations.<br>    Required for GitOps deployments if no other git server is available.<br>  actions:<br>    onDeploy:<br>      after:<br>      - maxTotalSeconds: 60<br>        maxRetries: 3<br>        cmd: ./zarf internal create-read-only-gitea-user<br>  charts:<br>  - name: gitea<br>    releaseName: zarf-gitea<br>    url: https://dl.gitea.io/charts<br>    version: 7.0.2<br>    namespace: zarf<br>    valuesFiles:<br>    - packages/gitea/gitea-values.yaml<br>  manifests:<br>  - name: git-connect<br>    namespace: zarf<br>    files:<br>    - packages/gitea/connect.yaml<br>  images:<br>  - gitea/gitea:1.18.3<br>variables:<br>- name: K3S_ARGS<br>  description: Arguments to pass to K3s<br>  default: --disable traefik<br>- name: REGISTRY_EXISTING_PVC<br>  description: &quot;Optional: Use an existing PVC for the registry instead of creating a new one. If this is set, the REGISTRY_PVC_SIZE variable will be ignored.&quot;<br>- name: REGISTRY_PVC_SIZE<br>  description: The size of the persistent volume claim for the registry<br>  default: 20Gi<br>- name: REGISTRY_CPU_REQ<br>  description: The CPU request for the registry<br>  default: 100m<br>- name: REGISTRY_MEM_REQ<br>  description: The memory request for the registry<br>  default: 256Mi<br>- name: REGISTRY_CPU_LIMIT<br>  description: The CPU limit for the registry<br>  default: &quot;3&quot;<br>- name: REGISTRY_MEM_LIMIT<br>  description: The memory limit for the registry<br>  default: 2Gi<br>- name: REGISTRY_HPA_MIN<br>  description: The minimum number of registry replicas<br>  default: &quot;1&quot;<br>- name: REGISTRY_HPA_MAX<br>  description: The maximum number of registry replicas<br>  default: &quot;5&quot;<br>- name: REGISTRY_HPA_ENABLE<br>  description: Enable the Horizontal Pod Autoscaler for the registry<br>  default: &quot;true&quot;<br>- name: GIT_SERVER_EXISTING_PVC<br>  description: &quot;Optional: Use an existing PVC for the git server instead of creating a new one. If this is set, the GIT_SERVER_PVC_SIZE variable will be ignored.&quot;<br>- name: GIT_SERVER_PVC_SIZE<br>  description: The size of the persistent volume claim for git server<br>  default: 10Gi<br>- name: GIT_SERVER_CPU_REQ<br>  description: The CPU request for git server<br>  default: 200m<br>- name: GIT_SERVER_MEM_REQ<br>  description: The memory request for git server<br>  default: 512Mi<br>- name: GIT_SERVER_CPU_LIMIT<br>  description: The CPU limit for git server<br>  default: &quot;3&quot;<br>- name: GIT_SERVER_MEM_LIMIT<br>  description: The memory limit for git server<br>  default: 2Gi<br>constants:<br>- name: AGENT_IMAGE<br>  value: agent:v0.24.2<br>This package has 9 artifacts with software bill-of-materials (SBOM) included. You can view them now<br>in the zarf-sbom folder in this directory or to go directly to one, open this in your browser:<br>/Users/jason/src/github.com/defenseunicorns/zarf-sbom/sbom-viewer-docker.io_grafana_promtail_2.7.0.html<br><br>* This directory will be removed after package deployment.<br><br>? Deploy this Zarf package? Yes<br>───────────────────────────────────────────────────────────────────────────────────────<br>name: logging<br>charts:<br>- name: loki-stack<br>  releaseName: zarf-loki-stack<br>  url: https://grafana.github.io/helm-charts<br>  version: 2.8.9<br>  namespace: zarf<br>  valuesFiles:<br>  - packages/logging-pgl/pgl-values.yaml<br>manifests:<br>- name: logging-connect<br>  namespace: zarf<br>  files:<br>  - packages/logging-pgl/connect.yaml<br>images:<br>- docker.io/grafana/promtail:2.7.0<br>- grafana/grafana:8.3.5<br>- grafana/loki:2.6.1<br>- quay.io/kiwigrid/k8s-sidecar:1.19.2<br><br>Deploys the Promtail Grafana &amp; Loki (PGL) stack. Aggregates logs from different containers and<br>presents them in a web dashboard. Recommended if no other logging stack is deployed in the cluster.<br>? Deploy the logging component? No<br>───────────────────────────────────────────────────────────────────────────────────────<br>name: git-server<br>actions:<br>  onDeploy:<br>    after:<br>    - maxTotalSeconds: 60<br>      maxRetries: 3<br>      cmd: ./zarf internal create-read-only-gitea-user<br>charts:<br>- name: gitea<br>  releaseName: zarf-gitea<br>  url: https://dl.gitea.io/charts<br>  version: 7.0.2<br>  namespace: zarf<br>  valuesFiles:<br>  - packages/gitea/gitea-values.yaml<br>manifests:<br>- name: git-connect<br>  namespace: zarf<br>  files:<br>  - packages/gitea/connect.yaml<br>images:<br>- gitea/gitea:1.18.3<br><br>Deploys Gitea to provide git repositories for Kubernetes configurations. Required for GitOps<br>deployments if no other git server is available.<br>? Deploy the git-server component? No<br><br><br>  📦 ZARF-INJECTOR COMPONENT<br><br><br>  ✔  Copying 1 files<br>  ✔  Gathering cluster information<br>  ⠋  Attempting to bootstrap with the [k3d-mattermost-example-server-0]/rancher/mirrored-library-tr  ⠙  Attempting to bootstrap with the [k3d-mattermost-example-server-0]/rancher/mirrored-library-tr  ⠹  Attempting to bootstrap with the [k3d-mattermost-example-server-0]/rancher/mirrored-library-tr  ⠸  Attempting to bootstrap with the [k3d-mattermost-example-server-0]/rancher/mirrored-library-tr  ⠼  Attempting to bootstrap with the [k3d-mattermost-example-server-0]/rancher/mirrored-library-tr  ⠴  Attempting to bootstrap with the [k3d-mattermost-example-server-0]/rancher/mirrored-library-tr  ✔  Attempting to bootstrap the seed image into the cluster<br><br><br>  📦 ZARF-SEED-REGISTRY COMPONENT<br><br><br>  ✔  Loading the Zarf State from the Kubernetes cluster<br>  ✔  Processing helm chart docker-registry:1.0.0 from Zarf-generated helm chart<br><br><br>  📦 ZARF-REGISTRY COMPONENT<br><br><br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:61003/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Processing helm chart docker-registry:1.0.0 from Zarf-generated helm chart<br>  ✔  Starting helm chart generation registry-connect<br>  ⠋  Processing helm chart raw-init-zarf-registry-registry-connect:0.1.1677170366 from Zarf-generat  ✔  Processing helm chart raw-init-zarf-registry-registry-connect:0.1.1677170366 from Zarf-generated helm chart<br>  ✔  Starting helm chart generation kep-1755-registry-annotation<br>  ⠋  Processing helm chart raw-init-zarf-registry-kep-1755-registry-annotation:0.1.1677170366 from   ✔  Processing helm chart raw-init-zarf-registry-kep-1755-registry-annotation:0.1.1677170366 from Zarf-generated helm chart<br><br><br>  📦 ZARF-AGENT COMPONENT<br><br><br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:61015/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Starting helm chart generation zarf-agent<br>  ⠋  Processing helm chart raw-init-zarf-agent-zarf-agent:0.1.1677170366 from Zarf-generated helm c  ✔  Processing helm chart raw-init-zarf-agent-zarf-agent:0.1.1677170366 from Zarf-generated helm chart<br>  ✔  Zarf deployment complete<br><br><br>     Application | Username  | Password                 | Connect<br>     Registry    | zarf-push | QFFiAMQ4GBW6BJ01fc4czE2W | zarf connect registry<br>doug in ~/src/github.com/defenseunicorns 🦄</pre><h3>Configure PostgreSQL Database</h3><ul><li>Navigate to the postgres-operator example.</li></ul><pre>doug in ~/src/github.com/defenseunicorns 🦄 cd zarf/examples/postgres-operator<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄  </pre><ul><li>Create postgres-operator package using the zarf package create command.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄 zarf package cr<br>eate .<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-11-45-50-1378292225.log<br><br>Using build directory .<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: postgres-operator-demo<br>  description: Demo of prod-like Postgres database(s) on an edge cluster<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 11:45:50 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: postgres-operator<br>  required: true<br>  charts:<br>  - name: postgres-operator<br>    url: https://opensource.zalando.com/postgres-operator/charts/postgres-operator<br>    version: 1.8.2<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - postgres/operator-values.yaml<br>  - name: postgres-operator-ui<br>    url: https://opensource.zalando.com/postgres-operator/charts/postgres-operator-ui<br>    version: 1.8.2<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - postgres/operator-ui-values.yaml<br>  manifests:<br>  - name: postgres-operator-zarf-connect<br>    files:<br>    - postgres/zarf-connect.yaml<br>  images:<br>  - registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.2<br>  - registry.opensource.zalan.do/acid/postgres-operator:v1.8.2<br>  - registry.opensource.zalan.do/acid/pgbouncer:master-22<br>  - registry.opensource.zalan.do/acid/spilo-14:2.1-p6<br>- name: pgadmin<br>  required: true<br>  charts:<br>  - name: pgadmin4<br>    url: https://helm.runix.net<br>    version: 1.11.0<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - pgadmin/values.yaml<br>  manifests:<br>  - name: pgadmin-zarf-connect<br>    files:<br>    - pgadmin/zarf-connect.yaml<br>  images:<br>  - docker.io/dpage/pgadmin4:6.10<br>- name: example-db<br>  manifests:<br>  - name: example-db<br>    files:<br>    - example-db/demo-cluster.yaml<br>variables:<br>- name: PGADMIN_PASSWORD<br>  prompt: true<br>? Create this Zarf package? Yes<br><br>Specify a maximum file size for this package in Megabytes. Above this size, the package will be<br>split into multiple files. 0 will disable this feature.<br>? Please provide a value for &quot;Maximum Package Size&quot; 0<br><br><br>  📦 POSTGRES-OPERATOR COMPONENT<br><br><br>  ⠋  Processing helm chart postgres-operator:1.8.2 from repo https://opensource.zalando.com/postgre  ⠙  Processing helm chart postgres-operator:1.8.2 from repo https://opensource.zalando.com/postgre  ✔  Processing helm chart postgres-operator:1.8.2 from repo https://opensource.zalando.com/postgres-operator/charts/postgres-operator<br>  ⠋  Processing helm chart postgres-operator-ui:1.8.2 from repo https://opensource.zalando.com/post  ✔  Processing helm chart postgres-operator-ui:1.8.2 from repo https://opensource.zalando.com/postgres-operator/charts/postgres-operator-ui<br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 PGADMIN COMPONENT<br><br><br>  ✔  Processing helm chart pgadmin4:1.11.0 from repo https://helm.runix.net<br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 EXAMPLE-DB COMPONENT<br><br><br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 COMPONENT IMAGES<br><br><br>  ⠋  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠙  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠹  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠸  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠼  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠴  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠦  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠧  Fetching image metadata (1 of 5): registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.  ⠇  Fetching image metadata (2 of 5): registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 (  ⠏  Fetching image metadata (2 of 5): registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 (  ⠋  Fetching image metadata (2 of 5): registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 (  ⠙  Fetching image metadata (2 of 5): registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 (  ✔  Loading metadata for 5 images.<br>     Pulling 5 images (272.55 MBs o^C659.41 MBs) ██████████                41% | 1m3s<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄 zarf package create .<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-11-47-08-100862483.log<br><br>Using build directory .<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: postgres-operator-demo<br>  description: Demo of prod-like Postgres database(s) on an edge cluster<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 11:47:08 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: postgres-operator<br>  required: true<br>  charts:<br>  - name: postgres-operator<br>    url: https://opensource.zalando.com/postgres-operator/charts/postgres-operator<br>    version: 1.8.2<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - postgres/operator-values.yaml<br>  - name: postgres-operator-ui<br>    url: https://opensource.zalando.com/postgres-operator/charts/postgres-operator-ui<br>    version: 1.8.2<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - postgres/operator-ui-values.yaml<br>  manifests:<br>  - name: postgres-operator-zarf-connect<br>    files:<br>    - postgres/zarf-connect.yaml<br>  images:<br>  - registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.2<br>  - registry.opensource.zalan.do/acid/postgres-operator:v1.8.2<br>  - registry.opensource.zalan.do/acid/pgbouncer:master-22<br>  - registry.opensource.zalan.do/acid/spilo-14:2.1-p6<br>- name: pgadmin<br>  required: true<br>  charts:<br>  - name: pgadmin4<br>    url: https://helm.runix.net<br>    version: 1.11.0<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - pgadmin/values.yaml<br>  manifests:<br>  - name: pgadmin-zarf-connect<br>    files:<br>    - pgadmin/zarf-connect.yaml<br>  images:<br>  - docker.io/dpage/pgadmin4:6.10<br>- name: example-db<br>  manifests:<br>  - name: example-db<br>    files:<br>    - example-db/demo-cluster.yaml<br>variables:<br>- name: PGADMIN_PASSWORD<br>  prompt: true<br>? Create this Zarf package? Yes<br><br>Specify a maximum file size for this package in Megabytes. Above this size, the package will be<br>split into multiple files. 0 will disable this feature.<br>? Please provide a value for &quot;Maximum Package Size&quot; 0<br><br><br>  📦 POSTGRES-OPERATOR COMPONENT<br><br><br>  ✔  Processing helm chart postgres-operator:1.8.2 from repo https://opensource.zalando.com/postgres-operator/charts/postgres-operator<br>  ✔  Processing helm chart postgres-operator-ui:1.8.2 from repo https://opensource.zalando.com/postgres-operator/charts/postgres-operator-ui<br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 PGADMIN COMPONENT<br><br><br>  ✔  Processing helm chart pgadmin4:1.11.0 from repo https://helm.runix.net<br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 EXAMPLE-DB COMPONENT<br><br><br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 COMPONENT IMAGES<br><br><br>  ✔  Loading metadata for 5 images.<br>  ✔  Pulling 5 images (659.41 MBs)<br>  ✔  Creating SBOMs for 5 images and 0 components with files.</pre><ul><li>Deploy the PostgreSQL operator with the zarf package deploy command.</li><li>You’ll be prompted to create a PGADMIN password, make note of this you’ll need it to create the PostgreSQL database.</li><li>Also say “y”es to the prompted for the example database. We’ll use it for Mattermost.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄 zarf package deploy zarf-package-postgres-operator-demo-arm64.tar.zst<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-11-53-23-1686449327.log<br>  ✔  Loading Zarf Package zarf-package-postgres-operator-demo-arm64.tar.zst<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: postgres-operator-demo<br>  description: Demo of prod-like Postgres database(s) on an edge cluster<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 11:47:08 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: postgres-operator<br>  required: true<br>  charts:<br>  - name: postgres-operator<br>    url: https://opensource.zalando.com/postgres-operator/charts/postgres-operator<br>    version: 1.8.2<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - postgres/operator-values.yaml<br>  - name: postgres-operator-ui<br>    url: https://opensource.zalando.com/postgres-operator/charts/postgres-operator-ui<br>    version: 1.8.2<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - postgres/operator-ui-values.yaml<br>  manifests:<br>  - name: postgres-operator-zarf-connect<br>    files:<br>    - postgres/zarf-connect.yaml<br>  images:<br>  - registry.opensource.zalan.do/acid/postgres-operator-ui:v1.8.2<br>  - registry.opensource.zalan.do/acid/postgres-operator:v1.8.2<br>  - registry.opensource.zalan.do/acid/pgbouncer:master-22<br>  - registry.opensource.zalan.do/acid/spilo-14:2.1-p6<br>- name: pgadmin<br>  required: true<br>  charts:<br>  - name: pgadmin4<br>    url: https://helm.runix.net<br>    version: 1.11.0<br>    namespace: postgres-operator<br>    valuesFiles:<br>    - pgadmin/values.yaml<br>  manifests:<br>  - name: pgadmin-zarf-connect<br>    files:<br>    - pgadmin/zarf-connect.yaml<br>  images:<br>  - docker.io/dpage/pgadmin4:6.10<br>- name: example-db<br>  manifests:<br>  - name: example-db<br>    files:<br>    - example-db/demo-cluster.yaml<br>variables:<br>- name: PGADMIN_PASSWORD<br>  prompt: true<br>This package has 5 artifacts with software bill-of-materials (SBOM) included. You can view them now<br>in the zarf-sbom folder in this directory or to go directly to one, open this in your browser:<br>/Users/jason/src/github.com/defenseunicorns/zarf/examples/postgres-operator/zarf-sbom/sbom-viewer-docker.io_dpage_pgadmin4_6.10.html<br><br>* This directory will be removed after package deployment.<br><br>? Deploy this Zarf package? Yes<br>? Please provide a value for &quot;PGADMIN_PASSWORD&quot; 12345<br>───────────────────────────────────────────────────────────────────────────────────────<br>name: example-db<br>manifests:<br>- name: example-db<br>  files:<br>? Deploy the example-db component? Yes<br><br><br>  📦 POSTGRES-OPERATOR COMPONENT<br><br><br>  ✔  Loading the Zarf State from the Kubernetes cluster<br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:61192/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Processing helm chart postgres-operator:1.8.2 from https://opensource.zalando.com/postgres-operator/charts/postgres-operator<br>  ✔  Processing helm chart postgres-operator-ui:1.8.2 from https://opensource.zalando.com/postgres-operator/charts/postgres-operator-ui<br>  ✔  Starting helm chart generation postgres-operator-zarf-connect<br>  ✔  Processing helm chart raw-postgres-operator-demo-postgres-operator-postgres-operator-zarf-connect:0.1.1677171203 from Zarf-generated helm chart<br><br><br>  📦 PGADMIN COMPONENT<br><br><br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:61239/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Processing helm chart pgadmin4:1.11.0 from https://helm.runix.net<br>  ✔  Starting helm chart generation pgadmin-zarf-connect<br>  ✔  Processing helm chart raw-postgres-operator-demo-pgadmin-pgadmin-zarf-connect:0.1.1677171203 from Zarf-generated helm chart<br><br><br>  📦 EXAMPLE-DB COMPONENT<br><br><br>  ✔  Starting helm chart generation example-db<br>  ✔  Processing helm chart raw-postgres-operator-demo-example-db-example-db:0.1.1677171203 from Zarf-generated helm chart<br>  ✔  Zarf deployment complete<br><br>     Connect Command                   | Description<br>     zarf connect postgres-operator-ui | Launch the postgres opertor web interface<br>     zarf connect pgadmin              | Launch the pgadmin web interface<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄</pre><p>Well, come back to this database later when we install Mattermost. For now, you can see everything working using kubectl</p><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄 kubectl get all -n postgres-operator<br>NAME                                        READY   STATUS    RESTARTS       AGE<br>pod/postgres-operator-6cf64f9c8c-fgz6z      1/1     Running   1 (138m ago)   138m<br>pod/postgres-operator-ui-84dc67cc44-4wl6c   1/1     Running   0              138m<br>pod/pgadmin4-d8544df47-vzq7c                1/1     Running   0              138m<br>pod/acid-zarf-test-1                        1/1     Running   0              18m<br>pod/acid-zarf-test-0                        1/1     Running   0              17m<br><br>NAME                                        TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE<br>service/postgres-operator                   ClusterIP   10.43.64.218    &lt;none&gt;        8080/TCP   138m<br>service/postgres-operator-ui                ClusterIP   10.43.200.226   &lt;none&gt;        80/TCP     138m<br>service/postgres-operator-ui-zarf-connect   ClusterIP   10.43.162.116   &lt;none&gt;        80/TCP     138m<br>service/pgadmin4                            ClusterIP   10.43.34.29     &lt;none&gt;        80/TCP     138m<br>service/pgadmin-zarf-connect                ClusterIP   10.43.38.201    &lt;none&gt;        80/TCP     136m<br>service/acid-zarf-test                      ClusterIP   10.43.185.13    &lt;none&gt;        5432/TCP   136m<br>service/acid-zarf-test-repl                 ClusterIP   10.43.36.173    &lt;none&gt;        5432/TCP   136m<br>service/acid-zarf-test-config               ClusterIP   None            &lt;none&gt;        &lt;none&gt;     136m<br><br>NAME                                   READY   UP-TO-DATE   AVAILABLE   AGE<br>deployment.apps/postgres-operator      1/1     1            1           138m<br>deployment.apps/postgres-operator-ui   1/1     1            1           138m<br>deployment.apps/pgadmin4               1/1     1            1           138m<br><br>NAME                                              DESIRED   CURRENT   READY   AGE<br>replicaset.apps/postgres-operator-6cf64f9c8c      1         1         1       138m<br>replicaset.apps/postgres-operator-ui-84dc67cc44   1         1         1       138m<br>replicaset.apps/pgadmin4-d8544df47                1         1         1       138m<br><br>NAME                              READY   AGE<br>statefulset.apps/acid-zarf-test   2/2     136m<br><br>NAME                                      TEAM   VERSION   PODS   VOLUME   CPU-REQUEST   MEMORY-REQUEST   AGE    STATUS<br>postgresql.acid.zalan.do/acid-zarf-test   acid   13        2      2Gi      100m          100Mi            136m   Running<br><br>NAME                                                    IMAGE                                               CLUSTER-LABEL   SERVICE-ACCOUNT   MIN-INSTANCES   AGE<br>operatorconfiguration.acid.zalan.do/postgres-operator   registry.opensource.zalan.do/acid/spilo-14:2.1-p6   cluster-name    postgres-pod      -1              138m<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄</pre><h3>Package and Deploy MinIO</h3><p>MinIO is used by Mattermost to store files, and again we can use the existing MinIO example with Zarf.</p><ul><li>Navigate to the MinIO example in the Zarf source code.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/postgres-operator on main 🦄 cd ../minio<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄</pre><p><strong>Note:</strong> While authoring this blog post, I found a bug in the MinIO example. I’ll be changing this documentation, but in the meantime, modify the zarf-connect.yaml. You’ll need to change the selector in the spec.</p><ul><li>Change this part of the selector</li></ul><pre>spec:<br>  selector:<br>    app.kubernetes.io/instance: zarf-minio-operator-console</pre><ul><li>To this</li></ul><pre>spec:<br>  selector:<br>    app.kubernetes.io/instance: minio-operator-console<br>    app.kubernetes.io/name: operator</pre><ul><li>Package the MinIO example using the zarf package create command.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 zarf package create .<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-14-17-55-691300379.log<br><br>Using build directory .<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: minio<br>  description: Deploy minio<br>  version: 4.3.7<br>  url: https://operator.min.io/<br>  image: https://raw.githubusercontent.com/minio/minio/master/.github/logo.svg?sanitize=true<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 14:17:55 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: minio<br>  required: true<br>  charts:<br>  - name: operator<br>    releaseName: minio-operator<br>    url: https://operator.min.io/<br>    version: 4.4.28<br>    namespace: minio-operator<br>    valuesFiles:<br>    - operator-values.yaml<br>  - name: tenant<br>    releaseName: minio-tenant<br>    url: https://operator.min.io/<br>    version: 4.4.28<br>    namespace: minio-operator<br>    valuesFiles:<br>    - tenant-values.yaml<br>  manifests:<br>  - name: zarf-connect<br>    files:<br>    - zarf-connect.yaml<br>  images:<br>  - minio/console:v0.19.4<br>  - minio/operator:v4.4.28<br>  - quay.io/minio/minio:RELEASE.2022-05-26T05-48-41Z<br>  - library/postgres:13<br>  - busybox:1.33.1<br>  - alpine<br>  - quay.io/prometheus/prometheus:latest<br>? Create this Zarf package? Yes<br><br>Specify a maximum file size for this package in Megabytes. Above this size, the package will be<br>split into multiple files. 0 will disable this feature.<br>? Please provide a value for &quot;Maximum Package Size&quot; 0<br><br><br>  📦 MINIO COMPONENT<br><br><br>  ✔  Processing helm chart operator:4.4.28 from repo https://operator.min.io/<br>  ✔  Processing helm chart tenant:4.4.28 from repo https://operator.min.io/<br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 COMPONENT IMAGES<br><br><br>  ✔  Loading metadata for 7 images. This step may take several seconds to complete.<br>  ✔  Pulling 7 images (467.19 MBs)<br>  ✔  Creating SBOMs for 7 images and 0 components with files.<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄</pre><ul><li>Now deploy the MinIO package you created with the zarf package deploy command.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 zarf package create .<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-14-17-55-691300379.log<br><br>Using build directory .<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: minio<br>  description: Deploy minio<br>  version: 4.3.7<br>  url: https://operator.min.io/<br>  image: https://raw.githubusercontent.com/minio/minio/master/.github/logo.svg?sanitize=true<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 14:17:55 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: minio<br>  required: true<br>  charts:<br>  - name: operator<br>    releaseName: minio-operator<br>    url: https://operator.min.io/<br>    version: 4.4.28<br>    namespace: minio-operator<br>    valuesFiles:<br>    - operator-values.yaml<br>  - name: tenant<br>    releaseName: minio-tenant<br>    url: https://operator.min.io/<br>    version: 4.4.28<br>    namespace: minio-operator<br>    valuesFiles:<br>    - tenant-values.yaml<br>  manifests:<br>  - name: zarf-connect<br>    files:<br>    - zarf-connect.yaml<br>  images:<br>  - minio/console:v0.19.4<br>  - minio/operator:v4.4.28<br>  - quay.io/minio/minio:RELEASE.2022-05-26T05-48-41Z<br>  - library/postgres:13<br>  - busybox:1.33.1<br>  - alpine<br>  - quay.io/prometheus/prometheus:latest<br>? Create this Zarf package? Yes<br><br>Specify a maximum file size for this package in Megabytes. Above this size, the package will be<br>split into multiple files. 0 will disable this feature.<br>? Please provide a value for &quot;Maximum Package Size&quot; 0<br><br><br>  📦 MINIO COMPONENT<br><br><br>  ✔  Processing helm chart operator:4.4.28 from repo https://operator.min.io/<br>  ✔  Processing helm chart tenant:4.4.28 from repo https://operator.min.io/<br>  ✔  Loading 1 K8s manifests<br><br><br>  📦 COMPONENT IMAGES<br><br><br>  ✔  Loading metadata for 7 images. This step may take several seconds to complete.<br>  ✔  Pulling 7 images (467.19 MBs)<br>  ✔  Creating SBOMs for 7 images and 0 components with files.<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 zarf package deploy zarf-package-minio-arm64-4.3.7.tar.zst<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-14-20-22-3365707464.log<br>  ✔  Loading Zarf Package zarf-package-minio-arm64-4.3.7.tar.zst<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: minio<br>  description: Deploy minio<br>  version: 4.3.7<br>  url: https://operator.min.io/<br>  image: https://raw.githubusercontent.com/minio/minio/master/.github/logo.svg?sanitize=true<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 14:17:55 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: minio<br>  required: true<br>  charts:<br>  - name: operator<br>    releaseName: minio-operator<br>    url: https://operator.min.io/<br>    version: 4.4.28<br>    namespace: minio-operator<br>    valuesFiles:<br>    - operator-values.yaml<br>  - name: tenant<br>    releaseName: minio-tenant<br>    url: https://operator.min.io/<br>    version: 4.4.28<br>    namespace: minio-operator<br>    valuesFiles:<br>    - tenant-values.yaml<br>  manifests:<br>  - name: zarf-connect<br>    files:<br>    - zarf-connect.yaml<br>  images:<br>  - minio/console:v0.19.4<br>  - minio/operator:v4.4.28<br>  - quay.io/minio/minio:RELEASE.2022-05-26T05-48-41Z<br>  - library/postgres:13<br>  - busybox:1.33.1<br>  - alpine<br>  - quay.io/prometheus/prometheus:latest<br>This package has 7 artifacts with software bill-of-materials (SBOM) included. You can view them now<br>in the zarf-sbom folder in this directory or to go directly to one, open this in your browser:<br>/Users/jason/src/github.com/defenseunicorns/zarf/examples/minio/zarf-sbom/sbom-viewer-alpine.html<br><br>* This directory will be removed after package deployment.<br><br>? Deploy this Zarf package? Yes<br><br><br>  📦 MINIO COMPONENT<br><br><br>  ✔  Loading the Zarf State from the Kubernetes cluster<br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:63299/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Processing helm chart operator:4.4.28 from https://operator.min.io/<br>  ✔  Processing helm chart tenant:4.4.28 from https://operator.min.io/<br>  ✔  Starting helm chart generation zarf-connect<br>  ✔  Processing helm chart raw-minio-minio-zarf-connect:0.1.1677180022 from Zarf-generated helm chart<br>  ✔  Zarf deployment complete<br><br>     Connect Command    | Description<br>     zarf connect minio | Launch the minio console, to get a JWT run:<br><br>     zarf tools kubectl -n minio-operator get secrets console-sa-secret -o jsonpath=&quot;{.data.token}&quot; | base64 --decode<br><br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄</pre><h3>Gathering the MinIO Credentials</h3><p>In order to connect to MinIO we’ll need the JWT token to authenticate with the MinIO console. The command was output at the end of the Zarf package deploy.</p><p><strong>Note: </strong>There’s a bug in the documentation here. The zarf tools command is attempting to process the -n argument for kubectl. You’ll get this error, the latest version of zarf as of the time of this blog post (i.e. v0.24.2). So use your own kubectl binary.</p><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 kubectl -n minio-operator get secrets console-sa-secret -o jsonpath=&quot;{.data.token}&quot; | base64 --decode<br>eyJhbGciOiJSUzI1NiIsImtpZCI6IjMzT1FZNlcxTzZmRkhVMFFPRy05WHVwZ3d4cmxxdF9ud2FybXV5SHBCWFUifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJtaW5pby1vcGVyYXRvciIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJjb25zb2xlLXNhLXNlY3JldCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJjb25zb2xlLXNhIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiMGFkNTY3ODYtMjRiOC00OGM4LWIyNzEtOTEwNjIwOWJiYTIwIiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Om1pbmlvLW9wZXJhdG9yOmNvbnNvbGUtc2EifQ.Xq7P7O2TPJIL8lSaXLH_Z_0vrrfdohMqxdl4zlGo9KNuWs2QGKUWTEJvH4M7Cd9rhl_4ggGpaPyOEH_jpDFHWC-UKXWC9c7lPzvYmc9M3FjsxFfutycCwGX5usIWHfYd4PfeMD952ItWpJDIYkkJb6QFdBFMF7lpi9v1XEaWQObKEZ5CYHT15zAwYcU3JwJm5ruPrzCBGVLuTtSnTtLPCXfSuxNVEiHK2ueATpNJJdCEI7GCUSPsaOhTuhK91P73MfXDkq_bVNDoLfNM7aZ8SBIaiC69tb2raH-EMjNgP9hEPGf_9PeOaDzHB1WaZ4b-UxHPkRhjJamcMAMAXDExJQ%<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄</pre><h3>Configuring MinIO</h3><ul><li>Once the MinIO infrastructure is stable, you can connect to the MinIO console. To see if everything is ready, you can use the kubectl command. Wait until all the pods are running</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main ● 🦄 kubectl get all -n minio-operator<br>NAME                                         READY   STATUS    RESTARTS      AGE<br>pod/console-c84ff4894-n7gs8                  1/1     Running   0             51s<br>pod/minio-operator-554c9f446f-wqtj9          1/1     Running   0             51s<br>pod/minio-operator-554c9f446f-zg7wj          1/1     Running   0             51s<br>pod/minio1-log-0                             1/1     Running   0             38s<br>pod/minio1-log-search-api-85c4d558c6-v26xq   1/1     Running   2 (35s ago)   38s<br>pod/minio1-ss-0-0                            1/1     Running   0             40s<br><br>NAME                                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE<br>service/operator                     ClusterIP   10.43.234.193   &lt;none&gt;        4222/TCP            51s<br>service/console                      ClusterIP   10.43.137.182   &lt;none&gt;        9090/TCP,9443/TCP   51s<br>service/minio-console-zarf-connect   ClusterIP   10.43.40.24     &lt;none&gt;        9443/TCP            48s<br>service/minio                        ClusterIP   10.43.65.130    &lt;none&gt;        443/TCP             42s<br>service/minio1-console               ClusterIP   10.43.121.217   &lt;none&gt;        9443/TCP            41s<br>service/minio1-hl                    ClusterIP   None            &lt;none&gt;        9000/TCP            41s<br>service/minio1-log-hl-svc            ClusterIP   None            &lt;none&gt;        5432/TCP            39s<br>service/minio1-log-search-api        ClusterIP   10.43.24.251    &lt;none&gt;        8080/TCP            38s<br><br>NAME                                    READY   UP-TO-DATE   AVAILABLE   AGE<br>deployment.apps/console                 1/1     1            1           51s<br>deployment.apps/minio-operator          2/2     2            2           51s<br>deployment.apps/minio1-log-search-api   1/1     1            1           38s<br><br>NAME                                               DESIRED   CURRENT   READY   AGE<br>replicaset.apps/console-c84ff4894                  1         1         1       51s<br>replicaset.apps/minio-operator-554c9f446f          2         2         2       51s<br>replicaset.apps/minio1-log-search-api-85c4d558c6   1         1         1       38s<br><br>NAME                           READY   AGE<br>statefulset.apps/minio1-log    1/1     39s<br>statefulset.apps/minio1-ss-0   1/1     40s<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main ● 🦄</pre><ul><li>Use the zarf connect command to connect to the MinIO console.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 zarf connect minio<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-15-05-07-2545738381.log<br>  ⠋  Looking for a Zarf Connect Label in the cluster (0s)<br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:64431<br>http://127.0.0.1:64431</pre><ul><li>This will open your web browser if it doesn’t, you can navigate to the tunnel created by the zarf connect command. In the example above, that’s http://127.0.0.1:64431</li><li>Use the JWT string you received in the Gathering The MinIO Credentials step. To review that command is below. If the % is rendered, ignore it. It’s an end-of-line artifact.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 kubectl -n minio-operator get secrets console-sa-secret -o jsonpath=&quot;{.data.token}&quot; | base64 --decode<br>eyJhbGciOiJSUzI1NiIsImtpZCI6IjMzT1FZNlcxTzZmRkhVMFFPRy05WHVwZ3d4cmxxdF9ud2FybXV5SHBCWFUifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJtaW5pby1vcGVyYXRvciIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJjb25zb2xlLXNhLXNlY3JldCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJjb25zb2xlLXNhIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiMGFkNTY3ODYtMjRiOC00OGM4LWIyNzEtOTEwNjIwOWJiYTIwIiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Om1pbmlvLW9wZXJhdG9yOmNvbnNvbGUtc2EifQ.Xq7P7O2TPJIL8lSaXLH_Z_0vrrfdohMqxdl4zlGo9KNuWs2QGKUWTEJvH4M7Cd9rhl_4ggGpaPyOEH_jpDFHWC-UKXWC9c7lPzvYmc9M3FjsxFfutycCwGX5usIWHfYd4PfeMD952ItWpJDIYkkJb6QFdBFMF7lpi9v1XEaWQObKEZ5CYHT15zAwYcU3JwJm5ruPrzCBGVLuTtSnTtLPCXfSuxNVEiHK2ueATpNJJdCEI7GCUSPsaOhTuhK91P73MfXDkq_bVNDoLfNM7aZ8SBIaiC69tb2raH-EMjNgP9hEPGf_9PeOaDzHB1WaZ4b-UxHPkRhjJamcMAMAXDExJQ%<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄</pre><figure><img alt="Screenshot of the Minio Console with the JWT input into the text box for Login." src="https://cdn-images-1.medium.com/max/842/1*HZjPYXvpNNbrrvQQbgesig.png" /></figure><h3>Create a Bucket for Object Storage in the default MinIO Tenant</h3><ul><li>Click on the minio1 tenant.</li></ul><figure><img alt="Screenshot of the MinIO Console, showing the minio1 tenant." src="https://cdn-images-1.medium.com/max/1024/1*XTd65bHRqguLstcyNqXgLw.png" /></figure><ul><li>In the minio1 tenant, click the Console button</li></ul><figure><img alt="Screenshot of the top of the minio1 tenant page, showing the Console button." src="https://cdn-images-1.medium.com/max/1024/1*VnD0fPN5wgWCfOtn1H3tLA.png" /></figure><ul><li>In the Tenants &gt; minio1 &gt; Management page, click the Create Bucket button.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x9J6vJefXrXeYQ0c7nMH0A.png" /></figure><ul><li>Give the bucket a name, and then click the Create Bucket button.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S9BqC-4MTU7tHu18kO-fnw.png" /></figure><ul><li>The Management page will now show the MinIO bucket that you created in the minio1 tenant.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKjqKxwkGCc9fl6t2NVeQA.png" /></figure><h3>Creating a MinIO Tenant User to MinIO Bucket access</h3><ul><li>Expand the Identity drop-down, and select Users.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B3V2V7cfopQJnvZ_Vn-vpQ.png" /></figure><ul><li>On the Users page, click the Create User button.</li></ul><figure><img alt="Screenshot of the Minio &gt; Tenant &gt; Users screen" src="https://cdn-images-1.medium.com/max/1024/1*ORBLBwRuOxI_QjUmpTHOsQ.png" /></figure><ul><li>Give the user a Username and Password, check the readwrite policy. Make note of these, you’ll need it to configure Mattermost.</li><li>Click the Save button.</li></ul><figure><img alt="Screenshot of the Management &gt; Create User screen with username, password and policies filled in." src="https://cdn-images-1.medium.com/max/1024/1*wLoSpAuZjb0cTeTpfH3lCw.png" /></figure><h3>Create a Mattermost Package</h3><ul><li>Create a new subdirectory for your Mattermost Zarf package.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 mkdir ../mattermost<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/minio on main 🦄 cd ../mattermost<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄</pre><ul><li>We’ll be creating 5 files.<br>- The Mattermost Operator<br>- A Mattermost Installation Manifest<br>- A PostgreSQL secret so Mattermost can access the PostgreSQL database.<br>- A MinIO secret so Mattermost can access the bucket you created earlier in the minio1 tenant.</li></ul><h3>Mattermost Operator</h3><ul><li>Get the URL for the Mattermost Operator from the document <a href="https://docs.mattermost.com/install/install-kubernetes.html">Install Mattermost on Kubernetes</a>. At the time of this blog post that operator can be found at <a href="https://raw.githubusercontent.com/mattermost/mattermost-operator/master/docs/mattermost-operator/mattermost-operator.yam">https://raw.githubusercontent.com/mattermost/mattermost-operator/master/docs/mattermost-operator/mattermost-operator.yam</a>l. Save this document to your mattermost folder as mattermost-operator.yaml</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 curl -LO https://raw.githubusercontent.com/mattermost/mattermost-operator/master/docs/mattermost-operator/mattermost-operator.yaml<br>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current<br>                                 Dload  Upload   Total   Spent    Left  Speed<br>100  409k  100  409k    0     0  1800k      0 --:--:-- --:--:-- --:--:-- 1851k<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 ls<br>mattermost-operator.yaml</pre><ul><li>We want to be explicit about which version of the Mattermost operator and container images we’re going to use.</li><li>Open the matttermost-operator.yaml file in your favorite editor, and scroll to the very bottom. Replace this :latest tag with the latest version of the mattermost-operator image. You can find this version at <a href="https://github.com/mattermost/mattermost-operator/releases">https://github.com/mattermost/mattermost-operator/releases</a>. At the time of this blog that is v1.19.0</li></ul><pre>     command:<br>        - /mattermost-operator<br>        env:<br>        - name: MAX_RECONCILING_INSTALLATIONS<br>          value: &quot;20&quot;<br>        - name: REQUEUE_ON_LIMIT_DELAY<br>          value: 20s<br>        - name: MAX_RECONCILE_CONCURRENCY<br>          value: &quot;10&quot;<br>        image: mattermost/mattermost-operator:latest # &lt;----- Replace this.<br>        imagePullPolicy: IfNotPresent<br>        name: mattermost-operator<br>        ports:<br>        - containerPort: 8383<br>          name: metrics<br>      serviceAccountName: mattermost-operator</pre><ul><li>In this case when you’re done, it should look like this.</li></ul><pre>      command:<br>        - /mattermost-operator<br>        env:<br>        - name: MAX_RECONCILING_INSTALLATIONS<br>          value: &quot;20&quot;<br>        - name: REQUEUE_ON_LIMIT_DELAY<br>          value: 20s<br>        - name: MAX_RECONCILE_CONCURRENCY<br>          value: &quot;10&quot;<br>        image: mattermost/mattermost-operator:v1.19.0<br>        imagePullPolicy: IfNotPresent<br>        name: mattermost-operator<br>        ports:<br>        - containerPort: 8383<br>          name: metrics<br>      serviceAccountName: mattermost-operator</pre><h3>Mattermost Installation Manifest</h3><ul><li>We’re skipping the nginx instructions as k3d uses <a href="https://k3s.io/">k3s</a>, which ships and enables <a href="https://traefik.io/">traefik</a> by default.</li><li>We’re skipping the license file since this is a getting-started blog.</li><li>Use your favorite editor, and copy the installation manifest.</li><li>Change the ingress.class to traefik.</li><li>Don’t forget to change your host as needed.</li><li>Scroll down to get the format for the sections needed for the MinIO and PostgreSQL secrets we’ll need to create.</li><li>Save the file as mattermost-installation.yaml. It will look like my example below. I changed the size to 100users. You’ll notice we’ll have to create secrets called minio-secret, and postgres-secret. You’ll also notice the bucket name is the same as the bucket I created in the MinIO console. The service name is the kubernetes default &lt;service name&gt;.&lt;namespace name&gt;.svc.cluster.local.</li></ul><pre>apiVersion: installation.mattermost.com/v1beta1<br>kind: Mattermost<br>metadata:<br>  name: mm-example-full                         # Chose the desired name<br>spec:<br>  size: 100users                               # Adjust to your requirements<br>  ingress:<br>    enabled: true<br>    host: example.mattermost-example.com        # Adjust to your domain<br>    annotations:<br>      kubernetes.io/ingress.class: traefik <br>  version: 6.0.1<br>  fileStore:<br>    external:<br>      url: minio.minio-operator.svc.cluster.local<br>      bucket: mattermost-bucket <br>      secret: minio-secret<br>  database:<br>    external:<br>      secret: postgres-secret<br>  licenseSecret: &quot;&quot;                             # If you have created secret in step 1, put its name here</pre><h3>PostgreSQL secret</h3><ul><li>Create a file called postgres-secret.yaml</li><li>Copy the format from the Mattermost documentation under Deploy Mattermost, step 3. That file looks like this.</li></ul><pre>apiVersion: v1<br>data:<br>  DB_CONNECTION_CHECK_URL: cG9zdGdyZXM6Ly91c2VyOnN1cGVyX3NlY3JldF9wYXNzd29yZEBteS1kYXRhYmFzZS5jbHVzdGVyLWFiY2QudXMtZWFzdC0xLnJkcy5hbWF6b25hd3MuY29tOjU0MzIvbWF0dGVybW9zdD9jb25uZWN0X3RpbWVvdXQ9MTAK<br>  DB_CONNECTION_STRING: cG9zdGdyZXM6Ly91c2VyOnN1cGVyX3NlY3JldF9wYXNzd29yZEBteS1kYXRhYmFzZS5jbHVzdGVyLWFiY2QudXMtZWFzdC0xLnJkcy5hbWF6b25hd3MuY29tOjU0MzIvbWF0dGVybW9zdD9jb25uZWN0X3RpbWVvdXQ9MTAK<br>  MM_SQLSETTINGS_DATASOURCEREPLICAS: cG9zdGdyZXM6Ly91c2VyOnN1cGVyX3NlY3JldF9wYXNzd29yZEBteS1kYXRhYmFzZS5jbHVzdGVyLXJvLWFiY2QudXMtZWFzdC0xLnJkcy5hbWF6b25hd3MuY29tOjU0MzIvbWF0dGVybW9zdD9jb25uZWN0X3RpbWVvdXQ9MTAK<br>kind: Secret<br>metadata:<br>  name: my-postgres-connection<br>type: Opaque</pre><ul><li>Remove the line with the DB_CONNECTION_CHECK_URL setting</li><li>Remove the line with the MM_SQLSETTINGS_DATASOURCEREPLICAS setting</li><li>Decode the DB_CONNECTION_STRING, we’re going to use it to get the connection string format.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 echo &quot;cG9zdGdyZXM6Ly91c2VyOnN1cGVyX3NlY3JldF9wYXNzd29yZEBteS1kYXRhYmFzZS5jbHVzdGVyLWFiY2QudXMtZWFzdC0xLnJkcy5hbWF6b25hd3MuY29tOjU0MzIvbWF0dGVybW9zdD9jb25uZWN0X3RpbWVvdXQ9MTAK&quot; | base64 -d<br>postgres://user:super_secret_password@my-database.cluster-abcd.us-east-1.rds.amazonaws.com:5432/mattermost?connect_timeout=10</pre><ul><li>Replace the username, password, server hostname, and database name, as per the <a href="https://docs.zarf.dev/examples/postgres-operator/">Zarf Postgres Operator example</a>.</li><li>The server hostname is acid-zarf-test.postgres-operator.svc.cluster.local</li><li>The database is zarf</li><li>The username is zarf</li><li>The password you can get from a Kubernetes secret using the kubectl command in the documentation. Again remember the % is an end-of-line token, not part of the password.</li></ul><pre>echo $(kubectl get secret zarf.acid-zarf-test.credentials.postgresql.acid.zalan.do -n postgres-operator --template={{.data.password}}) | base64 -d<br>HHqVPnTdd9dAH766unHsJMdkyBavk9mTUuiwFGOv9G7GdCelvVyS5wGrH8JJK8G4%<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄</pre><ul><li>In this case, that makes the Database Connection String</li></ul><pre>postgres://zarf:HHqVPnTdd9dAH766unHsJMdkyBavk9mTUuiwFGOv9G7GdCelvVyS5wGrH8JJK8G4@acid-zarf-test.postgres-operator.svc.cluster.local:5432/zarf?connect_timeout=10</pre><ul><li>This needs to be encoded for the Kubernetes secret.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 echo -n &quot;postgres://zarf:HHqVPnTdd9dAH766unHsJMdkyBavk9mTUuiwFGOv9G7GdCelvVyS5wGrH8JJK8G4@acid-zarf-test.postgres-operator.svc.cluster.local:5432/zarf?connect_timeout=10&quot; | base64<br>cG9zdGdyZXM6Ly96YXJmOkhIcVZQblRkZDlkQUg3NjZ1bkhzSk1ka3lCYXZrOW1UVXVpd0ZHT3Y5RzdHZENlbHZWeVM1d0dySDhKSks4RzRAYWNpZC16YXJmLXRlc3QucG9zdGdyZXMtb3BlcmF0b3Iuc3ZjLmNsdXN0ZXIubG9jYWw6NTQzMi96YXJmP2Nvbm5lY3RfdGltZW91dD0xMA==</pre><ul><li>In this example the postgres-secret.yaml file will look like this.</li></ul><pre>apiVersion: v1<br>data:<br>  DB_CONNECTION_STRING: cG9zdGdyZXM6Ly96YXJmOkhIcVZQblRkZDlkQUg3NjZ1bkhzSk1ka3lCYXZrOW1UVXVpd0ZHT3Y5RzdHZENlbHZWeVM1d0dySDhKSks4RzRAYWNpZC16YXJmLXRlc3QucG9zdGdyZXMtb3BlcmF0b3Iuc3ZjLmNsdXN0ZXIubG9jYWw6NTQzMi96YXJmP2Nvbm5lY3RfdGltZW91dD0xMA==<br>kind: Secret<br>metadata:<br>  name: postgres-secret<br>type: Opaque</pre><h3>MinIO Secret</h3><ul><li>Copy the format for the MinIO secret from the Mattermost documentation and save to a file called minio-secret.yaml. Under step 4. It will look something like this.</li></ul><pre>apiVersion: v1<br>data:<br>  accesskey: QUNDRVNTX0tFWQo=<br>  secretkey: U1VQRVJfU0VDUkVUX0tFWQo=<br>kind: Secret<br>metadata:<br>  name: my-s3-iam-access-key<br>type: Opaque</pre><ul><li>We’ll be replacing the accesskey and secretkey. We’ll also rename it to minio-secret.</li><li>The username will be the base64 encoded username you created when you created the Minio Tenant User in the minio1 tenant.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄  echo -n &quot;mattermost-user&quot; | base64<br>bWF0dGVybW9zdC11c2Vy</pre><ul><li>The password will be the base64 encodes password you created when you created the Minio Tenant User in the minio1 tenant.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 echo -n &quot;ReallyStrongMattermostPassword&quot; | base64<br>UmVhbGx5U3Ryb25nTWF0dGVybW9zdFBhc3N3b3Jk</pre><ul><li>With that the minio-secret.yaml file will look something like this.</li></ul><pre>apiVersion: v1<br>data:<br>  accesskey: bWF0dGVybW9zdC11c2Vy<br>  secretkey: UmVhbGx5U3Ryb25nTWF0dGVybW9zdFBhc3N3b3Jk<br>kind: Secret<br>metadata:<br>  name: minio-secret<br>type: Opaque</pre><h3>Zarf Package Manifest</h3><p>Now we’re ready to create our zarf.yaml file. Create a new file called zarf.yaml.</p><p>We’ll create items in the mattermost component for each of the files we’ve created and all of the images that are referenced by the mattermost operator.</p><p>The final package manifest will look something like this. You can get the version of the Mattermost Enterprise Edition Image at <a href="https://github.com/mattermost/mattermost-server/releases">https://github.com/mattermost/mattermost-server/releases</a></p><pre>kind: ZarfPackageConfig<br>metadata:<br>  name: mattermost-example<br>  description: &quot;Deploy Mattermost&quot;<br>  version: v1.19.0<br>  url: https://mattermost.com<br>  image: https://avatars.githubusercontent.com/u/9828093?s=200&amp;v=4<br>components:<br>  - name: mattermost<br>    required: true<br>    images:<br>      - &quot;mattermost/mattermost-operator:v1.19.0&quot;<br>      - &quot;mattermost/mattermost-enterprise-edition:7.8.0&quot;<br>    manifests:<br>      - name: mattermost-operator-installation<br>        namespace: mattermost-operator<br>        files: <br>          - &quot;mattermost-operator.yaml&quot;<br>      - name: postgres-secret<br>        files:<br>          - &quot;postgres-secret.yaml&quot;<br>      - name: minio-secret<br>        files:<br>          - &quot;minio-secret.yaml&quot;<br>      - name: mattermost-installation-manifest<br>        files:<br>          - &quot;mattermost-installation.yaml&quot;</pre><h3>Build the Zarf Package</h3><ul><li>Use the zarf package createcommand to build the package.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 zarf package create .<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-18-12-32-3214058833.log<br><br>Using build directory .<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: mattermost-example<br>  description: Deploy Mattermost<br>  version: v1.19.0<br>  url: https://mattermost.com<br>  image: https://avatars.githubusercontent.com/u/9828093?s=200&amp;v=4<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 18:12:32 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: mattermost<br>  required: true<br>  manifests:<br>  - name: mattermost-operator-installation<br>    namespace: mattermost-operator<br>    files:<br>    - mattermost-operator.yaml<br>  - name: postgres-secret<br>    files:<br>    - postgres-secret.yaml<br>  - name: minio-secret<br>    files:<br>    - minio-secret.yaml<br>  - name: mattermost-installation-manifest<br>    files:<br>    - mattermost-installation.yaml<br>  images:<br>  - mattermost/mattermost-operator:v1.19.0<br>  - mattermost/mattermost-enterprise-edition:7.8.0<br>? Create this Zarf package? Yes<br><br>Specify a maximum file size for this package in Megabytes. Above this size, the package will be<br>split into multiple files. 0 will disable this feature.<br>? Please provide a value for &quot;Maximum Package Size&quot; 0<br><br><br>  📦 MATTERMOST COMPONENT<br><br><br>  ✔  Loading 4 K8s manifests<br><br><br>  📦 COMPONENT IMAGES<br><br><br>  ✔  Loading metadata for 2 images.<br>  ✔  Pulling 2 images (493.24 MBs)<br>  ✔  Creating SBOMs for 2 images and 0 components with files.</pre><h3>Deploy the Mattermost Zarf Package</h3><ul><li>Use the zarf package deploy command to deploy the Zarf package you created.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 zarf package deploy zarf-package-mattermost-example-arm64-v1.19.0.tar.zst<br><br>Saving log file to<br>/var/folders/bk/rz1xx2sd5zn134c0_j1s2n5r0000gp/T/zarf-2023-02-23-18-13-47-3169555226.log<br>  ✔  Loading Zarf Package zarf-package-mattermost-example-arm64-v1.19.0.tar.zst<br><br>kind: ZarfPackageConfig<br>metadata:<br>  name: mattermost-example<br>  description: Deploy Mattermost<br>  version: v1.19.0<br>  url: https://mattermost.com<br>  image: https://avatars.githubusercontent.com/u/9828093?s=200&amp;v=4<br>  architecture: arm64<br>build:<br>  terminal: JvBUnicornMBP5<br>  user: jason<br>  architecture: arm64<br>  timestamp: Thu, 23 Feb 2023 18:12:32 -0500<br>  version: v0.24.2<br>  migrations:<br>  - scripts-to-actions<br>components:<br>- name: mattermost<br>  required: true<br>  manifests:<br>  - name: mattermost-operator-installation<br>    namespace: mattermost-operator<br>    files:<br>    - mattermost-operator.yaml<br>  - name: postgres-secret<br>    files:<br>    - postgres-secret.yaml<br>  - name: minio-secret<br>    files:<br>    - minio-secret.yaml<br>  - name: mattermost-installation-manifest<br>    files:<br>    - mattermost-installation.yaml<br>  images:<br>  - mattermost/mattermost-operator:v1.19.0<br>  - mattermost/mattermost-enterprise-edition:7.8.0<br>This package has 2 artifacts with software bill-of-materials (SBOM) included. You can view them now<br>in the zarf-sbom folder in this directory or to go directly to one, open this in your browser:<br>/Users/jason/src/github.com/defenseunicorns/zarf/examples/mattermost/zarf-sbom/sbom-viewer-mattermost_mattermost-enterprise-edition_7.8.0.html<br><br>* This directory will be removed after package deployment.<br><br>? Deploy this Zarf package? Yes<br><br><br>  📦 MATTERMOST COMPONENT<br><br><br>  ✔  Loading the Zarf State from the Kubernetes cluster<br>  ✔  Creating port forwarding tunnel at http://127.0.0.1:52578/v2/_catalog<br>  ✔  Storing images in the zarf registry<br>  ✔  Starting helm chart generation mattermost-operator-installation<br>  ✔  Processing helm chart raw-mattermost-example-mattermost-mattermost-operator-installation:0.1.1677194027 from Zarf-generated helm chart<br>  ✔  Starting helm chart generation postgres-secret<br>  ✔  Processing helm chart raw-mattermost-example-mattermost-postgres-secret:0.1.1677194027 from Zarf-generated helm chart<br>  ✔  Starting helm chart generation minio-secret<br>  ✔  Processing helm chart raw-mattermost-example-mattermost-minio-secret:0.1.1677194027 from Zarf-generated helm chart<br>  ✔  Starting helm chart generation mattermost-installation-manifest<br>  ✔  Processing helm chart raw-mattermost-example-mattermost-mattermost-installation-manifest:0.1.1677194027 from Zarf-generated helm chart<br>  ✔  Zarf deployment complete</pre><h3>Checking our work</h3><ul><li>Check your work with kubectl.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 kubectl -n mattermost-operator get all<br>NAME                                       READY   STATUS    RESTARTS   AGE<br>pod/mattermost-operator-7684b7d685-xs9sv   1/1     Running   0          104s<br><br>NAME                          TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE<br>service/mattermost-operator   ClusterIP   10.43.67.144   &lt;none&gt;        8383/TCP   104s<br><br>NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE<br>deployment.apps/mattermost-operator   1/1     1            1           104s<br><br>NAME                                             DESIRED   CURRENT   READY   AGE<br>replicaset.apps/mattermost-operator-7684b7d685   1         1         1       104s<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 kubectl get mattermosts.installation.mattermost.com<br>NAME              STATE         IMAGE   VERSION   ENDPOINT<br>mm-example-full   reconciling</pre><ul><li>When it’s ready, the mattermost installation will look like this.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 kubectl get mattermosts.installation.mattermost.com<br>NAME              STATE    IMAGE                                      VERSION   ENDPOINT<br>mm-example-full   stable   mattermost/mattermost-enterprise-edition   6.0.1     example.mattermost-example.com</pre><h3>Connecting to Mattermost</h3><ul><li>Use kubectl port-forward to connect to mattermost.</li></ul><pre>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 kubectl get svc<br>NAME              TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)             AGE<br>kubernetes        ClusterIP   10.43.0.1    &lt;none&gt;        443/TCP             6h48m<br>mm-example-full   ClusterIP   None         &lt;none&gt;        8065/TCP,8067/TCP   2m51s<br>doug in ~/src/github.com/defenseunicorns/zarf/examples/mattermost on main 🦄 kubectl port-forward svc/mm-example-full 8888:8065<br>Forwarding from 127.0.0.1:8888 -&gt; 8065<br>Forwarding from [::1]:8888 -&gt; 8065</pre><figure><img alt="Screenshot of a running Mattermost installation." src="https://cdn-images-1.medium.com/max/1024/1*tcWEwXHCbaMgHktCZIO5Mw.png" /></figure><h3>Closing</h3><p>Success! If this was helpful to you please let us know. If you have any questions you can reach us in the #Zarf channel on the <a href="https://slack.kubernetes.io/">Kubernetes Slack</a>. You can also reach us on <a href="https://twitter.com/DefenseUnicorns">Twitter</a>, <a href="https://www.linkedin.com/company/defense-unicorns">LinkedIn</a>, and <a href="https://www.youtube.com/@defenseunicorns">YouTube</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=638c9a306c75" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-unicorns/build-an-air-gap-mattermost-deployment-package-with-zarf-638c9a306c75">Build an Air Gap Mattermost Deployment Package with Zarf</a> was originally published in <a href="https://medium.com/defense-unicorns">Defense Unicorns</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Bill of Materials (SBOM) Comparison with Zarf]]></title>
            <link>https://medium.com/defense-unicorns/software-bill-of-materials-sbom-comparison-with-zarf-42f228973f6?source=rss-53c5592f6149------2</link>
            <guid isPermaLink="false">https://medium.com/p/42f228973f6</guid>
            <category><![CDATA[software-bill-of-material]]></category>
            <category><![CDATA[zarf]]></category>
            <dc:creator><![CDATA[Jason van Brackel]]></dc:creator>
            <pubDate>Mon, 27 Feb 2023 16:31:18 GMT</pubDate>
            <atom:updated>2023-02-27T16:31:18.704Z</atom:updated>
            <content:encoded><![CDATA[<p>Editor’s Note: This blog post includes significant contributions from <a href="https://medium.com/u/75e96a20c030">Lauren Mengert</a> and <a href="https://medium.com/u/acc764cb348a">Josi Moore</a>.</p><p><strong>Introduction</strong></p><p>Today we will cover the Software Bill of Materials (SBOM). We will then demonstrate the SBOM comparison tool provided by Zarf by creating and changing a Zarf package.</p><p><strong>Software Bill of Materials (SBOM)</strong></p><p>A Software Bill of Materials is a comprehensive list of all the components and dependencies used in a software project, inclusive of the name, version, source, authorship, and any relevant licenses or agreements associated with each component.</p><p>An SBOM is a component of ensuring a secure software supply chain. Organizations can quickly detect potential security risks and automate policy decisions regarding their software supply chains by clearly understanding the components and dependencies used in a project.</p><p><strong>SBOM Components</strong></p><ul><li>Provenance</li></ul><p>Software Provenance is the history of the development, creation, and distribution of a piece of software. It refers to information about a software artifact’s origin, dependencies, authorship, and evolution. This information is used to establish trust and credibility in the software and to track changes made to the software over time.</p><ul><li>Keys and Signatures</li></ul><p>A Public Key Infrastructure (PKI) employs key pairs, a public key and a private key, used to sign code, attestations, and products of the software build process. The private key signs these artifacts, which are later verified signed with the public key.</p><ul><li>Signatures</li></ul><p>These signatures are digital stamps of authenticity. They are used to verify software components’ origins. For example, a component checked with a public key was signed with a matching private key. However, signatures are not a claim of integrity but an authorship verification. Therefore, one must take great care to protect an organization’s private keys.</p><p>Signed artifacts within an SBOM may include but are not limited to, source code, binary artifacts, and container images.</p><ul><li>Attestations</li></ul><p>Attestations refer to a statement of assurance or certification verifying the accuracy and completeness of the information contained within the SBOM.</p><p><strong>SBOM Comparison with Zarf. Demo Time!</strong></p><p>A video demonstration of the steps below is available on YouTube.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmiZyG-jGEoQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmiZyG-jGEoQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmiZyG-jGEoQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6029ddcb4063fd6f99a7173d406d2655/href">https://medium.com/media/6029ddcb4063fd6f99a7173d406d2655/href</a></iframe><p><strong>Install Zarf</strong></p><ul><li>If you haven’t already, go to the <a href="https://zarf.dev/">Zarf website</a> and install Zarf by clicking the “install now” button and following the installation instructions. To learn more about the development of Zarf, <a href="https://github.com/defenseunicorns/zarf/releases">click here</a>.</li></ul><figure><img alt="Zarf website main page, with an arrow pointing to the INSTALL NOW button." src="https://cdn-images-1.medium.com/max/1024/0*898HhekC6VFZxYl6" /></figure><p><strong><em>NOTE:</em></strong> Make sure you have Zarf version 0.23.6 or later installed. The SBOM comparison tool will not work with any version before this. You can check your version by running the `zarf version` command.</p><figure><img alt="Screen shot of the zarf version command with the output 0.23.6" src="https://cdn-images-1.medium.com/max/638/0*4Wz6QOX-AhwsaMcU" /></figure><p><strong>Create Package</strong></p><ul><li>We’ll use the MinIO example in the Zarf repo for this demo. Ensure you are in your local terminal’s zarf/examples/minio path. You’ll need to <a href="https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository">clone</a> the <a href="https://github.com/defenseunicorns/zarf">Zarf repo</a> if you don’t already have it locally.</li></ul><figure><img alt="Screen shot of user navigating to the MinIO example path" src="https://cdn-images-1.medium.com/max/618/0*p6548rdih1nrxcs8" /></figure><ul><li>First, we’ll run `zarf package create,` passing everything in the minio folder to the command.</li></ul><figure><img alt="Screenshot running zarf package create command with its output." src="https://cdn-images-1.medium.com/max/780/0*09vWrusmlzkhmo1a" /></figure><ul><li>The output will show the package we’re creating.</li></ul><figure><img alt="ZarfPackageConfig yaml output that is part of the zarf package create command." src="https://cdn-images-1.medium.com/max/816/0*D-fHR9t4DHUIegTw" /></figure><ul><li>Then, it will ask us to verify that we want to create the package. Enter `Y` to confirm.</li><li>For ‘Maximum Package Size,’ enter `0` to disable the feature.</li></ul><figure><img alt="Screen shot with arrows pointing to where zarf prompts for input during package creation." src="https://cdn-images-1.medium.com/max/843/0*BplmgG0ru28Dgvlf" /></figure><p><strong>Create separate output for the SBOM.</strong></p><ul><li>To save the SBOM of the package, we need to run the `zarf package inspect — sbom-out sbom-old,` with `sbom-old` being what we’re naming the folder that will be created. You will need to pass the zarf package as well. If you haven’t changed directories, you should be able to tab complete the passing of the package.</li></ul><figure><img alt="Screenshot of the zarf package inspect command creating SBOM json files as output." src="https://cdn-images-1.medium.com/max/897/0*kdFAuOnbT8kMDjZj" /></figure><ul><li>List the directory contents with the <a href="https://man7.org/linux/man-pages/man1/ls.1.html">`ls`</a> command, and you’ll see the sbom-old folder that was created.</li></ul><figure><img alt="Output of the ls command with an arrow pointing to the created SBOM." src="https://cdn-images-1.medium.com/max/1024/0*aCnsdFkz68l5ULwn" /></figure><p><strong>Modify the software and create another SBOM.</strong></p><ul><li>Using your favorite text editor, open the zarf.yaml file</li></ul><figure><img alt="Screenshot of the operator opening the zarf.yaml file with vi." src="https://cdn-images-1.medium.com/max/647/0*fgl3Kuh5aAQi-zzp" /></figure><ul><li>At the time of this writing, the MinIO version used in the example is 4.4.28. Let’s update that to the latest version, 4.5.8. Change the highlighted lines to 4.5.8 and save the file.</li></ul><figure><img alt="Zarf.yaml file with boxes around the version numbers of the MinIO operator, and MinIO tenant helm charts, and the MinIO operator container image." src="https://cdn-images-1.medium.com/max/810/0*2PObOExIrrIIJjn3" /></figure><p><strong>Repeat steps 1–3</strong></p><ul><li>Run `zarf package create .`</li><li>Enter `Y` to confirm the creation of the package</li><li>Enter `0` for the Maximum package size</li><li>Once the package has been created, create a separate output for the SBOM by running `zarf package inspect — sbom-out <strong>sbom-new</strong>`. Notice that we’re naming this one <em>sbom-new</em>. Use tab completion to pass the file when you’re asked to ‘choose or type the package file’.</li><li>Run `ls` to make sure the sbom-new folder is there.</li></ul><p><strong>Open the toolset to make the SBOM comparison.</strong></p><ul><li>We can use the `inspect` action to open up the tool. Run `zarf package inspect — sbom` and use tab completion to pass the file when prompted to ‘choose or type the package file’.</li><li>The SBOM viewer should open in your browser. The compare tool is in the top right corner.</li></ul><figure><img alt="Screenshot of the Zarf SBOM Viewer webpage with an arrow pointing to the Compare Tool button." src="https://cdn-images-1.medium.com/max/1024/0*AmvimoF-qpQ0bhKm" /></figure><figure><img alt="Screenshot of the Zarf SBOM Comparison webpage with Old File and New File areas highligted." src="https://cdn-images-1.medium.com/max/1024/0*f0CS0ZeqZpfIQPl1" /></figure><ul><li>Once you’re in the comparison tool, upload the old file. `&lt;your-path-to-zarf&gt;/zarf/examples/minio/sbom-old/minio/minio_operator_v4.4.28.json`</li><li>It should look something like this:</li></ul><figure><img alt="Screenshot of a MacOS Finder window navigating to the Zarf &gt; examples folder." src="https://cdn-images-1.medium.com/max/1024/0*9js_iT2F79G1M72v" /></figure><figure><img alt="Screenshot of a MacOS Finder window navigating to the examples &gt; minio folder." src="https://cdn-images-1.medium.com/max/1024/0*abz8vzI4Qfiat31L" /></figure><figure><img alt="Screenshot of a MacOS Finder window navigating to the minio &gt; sbom-old  folder." src="https://cdn-images-1.medium.com/max/1024/0*hIW1lHcPT1Bt8z7N" /></figure><figure><img alt="Screenshot of a MacOS Finder window navigating to the sbom-old &gt; minio folder." src="https://cdn-images-1.medium.com/max/1024/0*s7quGMqifiejUl8M" /></figure><figure><img alt="Screenshot of a MacOS Finder window navigating to the minio_operator_v4.4.28.json file in the minio folder." src="https://cdn-images-1.medium.com/max/1024/0*DLXBb_o8hAodFy3u" /></figure><ul><li>Next, upload the new file. This should be identical to uploading the old file; the path will be slightly different. `&lt;your-path-to-zarf&gt;/zarf/examples/minio/sbom-new/minio/minio_operator_v4.5.8.json`</li><li>After uploading both files, hit the <strong>‘Run Comparison’</strong> button. This will show you any changes, additions, and removals.</li></ul><figure><img alt="Screenshot of the Zarf SBOM Comparison tool webpage with the Difference column highlighted in the table of SBOM changes between the Old File and New File." src="https://cdn-images-1.medium.com/max/1024/0*_NXkQYb8xW_u_Jxx" /></figure><p>That’s it! As you can see, the SBOM comparison tool allows us to easily compare two different SBOMs to see what has changed from version to version.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42f228973f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/defense-unicorns/software-bill-of-materials-sbom-comparison-with-zarf-42f228973f6">Software Bill of Materials (SBOM) Comparison with Zarf</a> was originally published in <a href="https://medium.com/defense-unicorns">Defense Unicorns</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>