{"id":23631059,"url":"https://github.com/chipwolf/k3s-sops-demo","last_synced_at":"2026-01-23T09:25:29.422Z","repository":{"id":49541511,"uuid":"358693718","full_name":"ChipWolf/k3s-sops-demo","owner":"ChipWolf","description":null,"archived":false,"fork":false,"pushed_at":"2021-06-15T12:09:57.000Z","size":35,"stargazers_count":0,"open_issues_count":13,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-05-18T23:09:35.419Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ChipWolf.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null}},"created_at":"2021-04-16T18:59:13.000Z","updated_at":"2021-04-16T18:59:18.000Z","dependencies_parsed_at":"2022-09-05T04:20:16.080Z","dependency_job_id":null,"html_url":"https://github.com/ChipWolf/k3s-sops-demo","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":"onedr0p/cluster-template","purl":"pkg:github/ChipWolf/k3s-sops-demo","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ChipWolf%2Fk3s-sops-demo","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ChipWolf%2Fk3s-sops-demo/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ChipWolf%2Fk3s-sops-demo/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ChipWolf%2Fk3s-sops-demo/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ChipWolf","download_url":"https://codeload.github.com/ChipWolf/k3s-sops-demo/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ChipWolf%2Fk3s-sops-demo/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28686236,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-23T05:48:07.525Z","status":"ssl_error","status_checked_at":"2026-01-23T05:48:07.129Z","response_time":59,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-12-28T02:48:27.092Z","updated_at":"2026-01-23T09:25:29.392Z","avatar_url":"https://github.com/ChipWolf.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Template for deploying k3s and Flux backed by SOPS secrets\n\nTemplate for creating a [k3s](https://k3s.io/) cluster with [k3sup](https://github.com/alexellis/k3sup).\n\nThe purpose here is to showcase how you can deploy an entire Kubernetes cluster and show it off to the world using the [GitOps](https://www.weave.works/blog/what-is-gitops-really) tool [Flux](https://toolkit.fluxcd.io/). With the [Flux SOPS integration](https://toolkit.fluxcd.io/guides/mozilla-sops/) you'll be able to commit encrypted secrets to your public repo.\n\nThe following components are installed in your [k3s](https://k3s.io/) cluster by default. They are only included to get a minimum viable cluster up and running. You are free to add / remove components to your liking but anything outside the scope of the below components are not supported by this template.\n\n- [flannel](https://github.com/flannel-io/flannel)\n- [local-path-provisioner](https://github.com/rancher/local-path-provisioner)\n- [flux](https://toolkit.fluxcd.io/)\n- [metallb](https://metallb.universe.tf/)\n- [cert-manager](https://cert-manager.io/) with Cloudflare DNS challenge\n- [ingress-nginx](https://kubernetes.github.io/ingress-nginx/)\n- [homer](https://github.com/bastienwirtz/homer)\n\n## Overview\n\n- [Prerequisites](https://github.com/k8s-at-home/template-cluster-k3s#memo-prerequisites)\n- [Lets go!](https://github.com/k8s-at-home/template-cluster-k3s#rocket-lets-go)\n- [Post installation](https://github.com/k8s-at-home/template-cluster-k3s#mega-post-installation)\n- [Debugging](https://github.com/k8s-at-home/template-cluster-k3s#point_right-debugging)\n- [Automation](https://github.com/k8s-at-home/template-cluster-k3s#robot-automation)\n- [What's next](https://github.com/k8s-at-home/template-cluster-k3s#grey_question-whats-next)\n- [Thanks](https://github.com/k8s-at-home/template-cluster-k3s#handshake-thanks)\n\n## :memo:\u0026nbsp; Prerequisites\n\n### :computer:\u0026nbsp; Nodes\n\nBare metal or VMs with any modern operating system like Ubuntu, Debian or CentOS.\n\n### :wrench:\u0026nbsp; Tools\n\n:round_pushpin: You need to install the required CLI tools listed below on your workstation.\n\n| Tool                                                               | Purpose                                                             | Minimum version | Required |\n|--------------------------------------------------------------------|---------------------------------------------------------------------|:---------------:|:--------:|\n| [k3sup](https://github.com/alexellis/k3sup)                        | Tool to install k3s on your nodes                                   |    `0.10.2`     |    ✅     |\n| [kubectl](https://kubernetes.io/docs/tasks/tools/)                 | Allows you to run commands against Kubernetes clusters              |    `1.21.0`     |    ✅     |\n| [flux](https://toolkit.fluxcd.io/)                                 | Operator that manages your k8s cluster based on your Git repository |    `0.12.3`     |    ✅     |\n| [SOPS](https://github.com/mozilla/sops)                            | Encrypts k8s secrets with GnuPG                                     |     `3.7.1`     |    ✅     |\n| [GnuPG](https://gnupg.org/)                                        | Encrypts and signs your data                                        |    `2.2.27`     |    ✅     |\n| [pinentry](https://gnupg.org/related_software/pinentry/index.html) | Allows GnuPG to read passphrases and PIN numbers                    |     `1.1.1`     |    ✅     |\n| [direnv](https://github.com/direnv/direnv)                         | Exports env vars based on present working directory                 |    `2.28.0`     |    ❌     |\n| [pre-commit](https://github.com/pre-commit/pre-commit)             | Runs checks during `git commit`                                     |    `2.12.0`     |    ❌     |\n| [kustomize](https://kustomize.io/)                                 | Template-free way to customize application configuration            |     `4.1.0`     |    ❌     |\n| [helm](https://helm.sh/)                                           | Manage Kubernetes applications                                      |     `3.5.4`     |    ❌     |\n\n## :warning:\u0026nbsp; Pre-installation\n\nIt's very important and I cannot stress enough, make sure you are not pushing your secrets un-encrypted to a public Git repo.\n\n### pre-commit\n\nIt is advisable to install [pre-commit](https://pre-commit.com/) and the pre-commit hooks that come with this repository.\n[sops-pre-commit](https://github.com/k8s-at-home/sops-pre-commit) will check to make sure you are not by accident commiting your secrets un-encrypted.\n\nAfter pre-commit is installed on your machine run:\n\n```sh\npre-commit install-hooks\n```\n\n## :rocket:\u0026nbsp; Lets go!\n\nVery first step will be to create a new repository by clicking the **Use this template** button on this page.\n\n:round_pushpin: In these instructions you will be exporting several environment variables to your current shell env. Make sure you stay with in your current shell to not lose any exported variables.\n\n### :closed_lock_with_key:\u0026nbsp; Setting up GnuPG keys\n\n:round_pushpin: Here we will create a personal and a Flux GPG key. Using SOPS with GnuPG allows us to encrypt and decrypt secrets.\n\n1. Create a Personal GPG Key, password protected, and export the fingerprint\n\n```sh\nexport GPG_TTY=$(tty)\nexport PERSONAL_KEY_NAME=\"First name Last name (location) \u003cemail\u003e\"\n\ngpg --batch --full-generate-key \u003c\u003cEOF\nKey-Type: 1\nKey-Length: 4096\nSubkey-Type: 1\nSubkey-Length: 4096\nExpire-Date: 0\nName-Real: ${PERSONAL_KEY_NAME}\nEOF\n\ngpg --list-secret-keys \"${PERSONAL_KEY_NAME}\"\n# pub   rsa4096 2021-03-11 [SC]\n#       772154FFF783DE317KLCA0EC77149AC618D75581\n# uid           [ultimate] k8s@home (Macbook) \u003ck8s-at-home@gmail.com\u003e\n# sub   rsa4096 2021-03-11 [E]\n\nexport PERSONAL_KEY_FP=772154FFF783DE317KLCA0EC77149AC618D75581\n```\n\n2. Create a Flux GPG Key and export the fingerprint\n\n```sh\nexport GPG_TTY=$(tty)\nexport FLUX_KEY_NAME=\"Cluster name (Flux) \u003cemail\u003e\"\n\ngpg --batch --full-generate-key \u003c\u003cEOF\n%no-protection\nKey-Type: 1\nKey-Length: 4096\nSubkey-Type: 1\nSubkey-Length: 4096\nExpire-Date: 0\nName-Real: ${FLUX_KEY_NAME}\nEOF\n\ngpg --list-secret-keys \"${FLUX_KEY_NAME}\"\n# pub   rsa4096 2021-03-11 [SC]\n#       AB675CE4CC64251G3S9AE1DAA88ARRTY2C009E2D\n# uid           [ultimate] Home cluster (Flux) \u003ck8s-at-home@gmail.com\u003e\n# sub   rsa4096 2021-03-11 [E]\n\nexport FLUX_KEY_FP=AB675CE4CC64251G3S9AE1DAA88ARRTY2C009E2D\n```\n\n### :sailboat:\u0026nbsp; Installing k3s with k3sup\n\n:round_pushpin: Here we will be install [k3s](https://k3s.io/) with [k3sup](https://github.com/alexellis/k3sup).\n\n1. Ensure you are able to SSH into you nodes with using your private ssh key. This is how k3sup is able to connect to your remote node.\n\n2. Install the master node\n\n```sh\nk3sup install \\\n    --host=169.254.1.1 \\\n    --user=k8s-at-home \\\n    --k3s-version=v1.20.5+k3s1 \\\n    --k3s-extra-args=\"--disable servicelb --disable traefik\"\n```\n\n3. Join a worker node(s) (optional)\n\n```sh\nk3sup join \\\n    --host=169.254.1.2 \\\n    --server-host=169.254.1.1 \\\n    --k3s-version=v1.20.5+k3s1 \\\n    --user=k8s-at-home\n```\n\n4. Verify the nodes are online\n   \n```sh\nkubectl --kubeconfig=./kubeconfig get nodes\n# NAME           STATUS   ROLES                       AGE     VERSION\n# k8s-master-a   Ready    control-plane,master      4d20h   v1.20.5+k3s1\n# k8s-worker-a   Ready    worker                    4d20h   v1.20.5+k3s1\n```\n\n### :cloud:\u0026nbsp; Cloudflare API Token\n\n:round_pushpin: In order to use cert-manager with the Cloudflare DNS challenge you will need to create a API token.\n\n1. Head over to Cloudflare and create a API token by going [here](https://dash.cloudflare.com/profile/api-tokens).\n2. Click the blue `Create Token` button\n3. Scroll down and create a Custom Token by choosing `Get started`\n4. Give your token a name like `cert-manager`\n5. Under `Permissions` give read access to `Zone` : `Zone` and `Zone` : `DNS`\n6. Under `Zone Resources` set it to `Include` : `All Zones`\n7. Click `Continue to summary` and then `Create Token`\n8. Export this token and your Cloudflare email address to an environment variable on your system to be used in the following steps\n\n```sh\nexport BOOTSTRAP_CLOUDFLARE_EMAIL=\"k8s-at-home@gmail.com\"\nexport BOOTSTRAP_CLOUDFLARE_TOKEN=\"kpG6iyg3FS_du_8KRShdFuwfbwu3zMltbvmJV6cD\"\n```\n\n### :small_blue_diamond:\u0026nbsp; GitOps with Flux\n\n:round_pushpin: Here we will be installing [flux](https://toolkit.fluxcd.io/) after some quick bootstrap steps.\n\n1. Verify Flux can be installed\n\n```sh\nflux --kubeconfig=./kubeconfig check --pre\n# ► checking prerequisites\n# ✔ kubectl 1.21.0 \u003e=1.18.0-0\n# ✔ Kubernetes 1.20.5+k3s1 \u003e=1.16.0-0\n# ✔ prerequisites checks passed\n```\n\n2. Pre-create the `flux-system` namespace\n\n```sh\nkubectl --kubeconfig=./kubeconfig create namespace flux-system --dry-run=client -o yaml | kubectl --kubeconfig=./kubeconfig apply -f -\n```\n\n3. Add the Flux GPG key in-order for Flux to decrypt SOPS secrets\n\n```sh\ngpg --export-secret-keys --armor \"${FLUX_KEY_FP}\" |\nkubectl --kubeconfig=./kubeconfig create secret generic sops-gpg \\\n    --namespace=flux-system \\\n    --from-file=sops.asc=/dev/stdin\n```\n\n4. Update files using `envsubst` or by updating the files listed below manually\n\n```sh\nexport BOOTSTRAP_GITHUB_REPOSITORY=\"https://github.com/k8s-at-home/home-cluster\"\nexport BOOTSTRAP_METALLB_LB_RANGE=\"169.254.1.10-169.254.1.20\"\nexport BOOTSTRAP_DOMAIN=\"k8s-at-home.com\"\nexport BOOTSTRAP_DOMAIN_CERT=\"k8s-at-home\"\nexport BOOTSTRAP_INGRESS_NGINX_LB=\"169.254.1.10\"\n\nenvsubst \u003c ./tmpl/.sops.yaml \u003e ./.sops.yaml\nenvsubst \u003c ./tmpl/cluster-secrets.yaml \u003e ./cluster/base/cluster-secrets.yaml\nenvsubst \u003c ./tmpl/cluster-settings.yaml \u003e ./cluster/base/cluster-settings.yaml\nenvsubst \u003c ./tmpl/gotk-sync.yaml \u003e ./cluster/base/flux-system/gotk-sync.yaml\nenvsubst \u003c ./tmpl/secret.enc.yaml \u003e ./cluster/core/cert-manager/secret.enc.yaml\n```\n\n5. **Verify** all the above files have the correct information present\n\n6. Encrypt `cluster/cluster-secrets.yaml` and `cert-manager/secret.enc.yaml` with SOPS\n\n```sh\nexport GPG_TTY=$(tty)\nsops --encrypt --in-place ./cluster/base/cluster-secrets.yaml\nsops --encrypt --in-place ./cluster/core/cert-manager/secret.enc.yaml\n```\n\n:round_pushpin: Variables defined in `cluster-secrets.yaml` and `cluster-settings.yaml` will be usable anywhere in your YAML manifests under `./cluster`\n\n7. **Verify** all the above files are **encrypted** with SOPS\n\n8. Push you changes to git\n\n```sh\ngit add -A\ngit commit -m \"initial commit\"\ngit push\n```\n\n9. Install Flux\n\n```sh\nkubectl --kubeconfig=./kubeconfig apply --kustomize=./cluster/base/flux-system\n# namespace/flux-system configured\n# customresourcedefinition.apiextensions.k8s.io/alerts.notification.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/buckets.source.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/gitrepositories.source.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/helmcharts.source.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/helmreleases.helm.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/helmrepositories.source.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/kustomizations.kustomize.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/providers.notification.toolkit.fluxcd.io created\n# customresourcedefinition.apiextensions.k8s.io/receivers.notification.toolkit.fluxcd.io created\n# serviceaccount/helm-controller created\n# serviceaccount/kustomize-controller created\n# serviceaccount/notification-controller created\n# serviceaccount/source-controller created\n# clusterrole.rbac.authorization.k8s.io/crd-controller-flux-system created\n# clusterrolebinding.rbac.authorization.k8s.io/cluster-reconciler-flux-system created\n# clusterrolebinding.rbac.authorization.k8s.io/crd-controller-flux-system created\n# service/notification-controller created\n# service/source-controller created\n# service/webhook-receiver created\n# deployment.apps/helm-controller created\n# deployment.apps/kustomize-controller created\n# deployment.apps/notification-controller created\n# deployment.apps/source-controller created\n# unable to recognize \"./cluster/base/flux-system\": no matches for kind \"Kustomization\" in version \"kustomize.toolkit.fluxcd.io/v1beta1\"\n# unable to recognize \"./cluster/base/flux-system\": no matches for kind \"GitRepository\" in version \"source.toolkit.fluxcd.io/v1beta1\"\n# unable to recognize \"./cluster/base/flux-system\": no matches for kind \"HelmRepository\" in version \"source.toolkit.fluxcd.io/v1beta1\"\n# unable to recognize \"./cluster/base/flux-system\": no matches for kind \"HelmRepository\" in version \"source.toolkit.fluxcd.io/v1beta1\"\n# unable to recognize \"./cluster/base/flux-system\": no matches for kind \"HelmRepository\" in version \"source.toolkit.fluxcd.io/v1beta1\"\n# unable to recognize \"./cluster/base/flux-system\": no matches for kind \"HelmRepository\" in version \"source.toolkit.fluxcd.io/v1beta1\"\n```\n\n:round_pushpin: Due to race conditions with the Flux CRDs you will have to run the command one more time. There should be no errors on this second run.\n\n```sh\nkubectl --kubeconfig=./kubeconfig apply --kustomize=./cluster/base/flux-system\n```\n\n## :mega:\u0026nbsp; Post installation\n\n### Verify Flux\n\n```sh\nkubectl --kubeconfig=./kubeconfig get pods -n flux-system\n# NAME                                       READY   STATUS    RESTARTS   AGE\n# helm-controller-5bbd94c75-89sb4            1/1     Running   0          1h\n# kustomize-controller-7b67b6b77d-nqc67      1/1     Running   0          1h\n# notification-controller-7c46575844-k4bvr   1/1     Running   0          1h\n# source-controller-7d6875bcb4-zqw9f         1/1     Running   0          1h\n```\n\n### Verify ingress\n\nIf your cluster is not accessible to outside world you can update your hosts file to verify the ingress controller is working.\n\n```sh\nsudo echo \"${BOOTSTRAP_INGRESS_NGINX_LB} ${BOOTSTRAP_DOMAIN} homer.${BOOTSTRAP_DOMAIN}\" \u003e\u003e /etc/hosts\n```\n\nHead over to your browser and you _should_ be able to access `https://homer.${BOOTSTRAP_DOMAIN}`\n\n### direnv\n\nThis is a great tool to export environment variables depending on what your present working directory is, head over to their [installation guide](https://direnv.net/docs/installation.html) and don't forget to hook it into your shell!\n\nWhen this is done you no longer have to use `--kubeconfig=./kubeconfig` in your `kubectl` or `flux` commands.\n\n### Delete Flux GPG key\n\nSince there is a GPG key specifically for Flux you can remove the secret key from your personal machine.\n\n```sh\ngpg --delete-secret-keys \"${FLUX_KEY_FP}\"\n```\n\n### VSCode SOPS extension\n\n[Here](https://marketplace.visualstudio.com/items?itemName=signageos.signageos-vscode-sops)'s a neat little plugin for those using VSCode.\nIt will automatically decrypt you SOPS secrets when you click on the file in the editor and encrypt them when you save the file.\n\n## :point_right:\u0026nbsp; Debugging\n\nManually sync Flux with your Git repository\n\n```sh\nflux --kubeconfig=./kubeconfig reconcile source git flux-system\n# ► annotating GitRepository flux-system in flux-system namespace\n# ✔ GitRepository annotated\n# ◎ waiting for GitRepository reconciliation\n# ✔ GitRepository reconciliation completed\n# ✔ fetched revision main/943e4126e74b273ff603aedab89beb7e36be4998\n```\n\nShow the health of you kustomizations\n\n```sh\nkubectl --kubeconfig=./kubeconfig get kustomization -A\n# NAMESPACE     NAME          READY   STATUS                                                             AGE\n# flux-system   apps          True    Applied revision: main/943e4126e74b273ff603aedab89beb7e36be4998    3d19h\n# flux-system   core          True    Applied revision: main/943e4126e74b273ff603aedab89beb7e36be4998    4d6h\n# flux-system   flux-system   True    Applied revision: main/943e4126e74b273ff603aedab89beb7e36be4998    4d6h\n```\n\nShow the health of your main Flux `GitRepository`\n\n```sh\nflux --kubeconfig=./kubeconfig get sources git\n# NAME           READY\tMESSAGE                                                            REVISION                                         SUSPENDED\n# flux-system    True \tFetched revision: main/943e4126e74b273ff603aedab89beb7e36be4998    main/943e4126e74b273ff603aedab89beb7e36be4998    False\n```\n\nShow the health of your `HelmRelease`s\n\n```sh\nflux --kubeconfig=./kubeconfig get helmrelease -A\n# NAMESPACE   \tNAME                  \tREADY\tMESSAGE                         \tREVISION\tSUSPENDED\n# cert-manager\tcert-manager          \tTrue \tRelease reconciliation succeeded\tv1.3.0  \tFalse\n# home        \thomer                 \tTrue \tRelease reconciliation succeeded\t4.2.0   \tFalse\n# networking  \tingress-nginx       \tTrue \tRelease reconciliation succeeded\t3.29.0  \tFalse\n```\n\nShow the health of your `HelmRepository`s\n\n```sh\nflux --kubeconfig=./kubeconfig get sources helm -A\n# NAMESPACE  \tNAME                 READY\tMESSAGE                                                   \tREVISION                                \tSUSPENDED\n# flux-system\tbitnami-charts       True \tFetched revision: 0ec3a3335ff991c45735866feb1c0830c4ed85cf\t0ec3a3335ff991c45735866feb1c0830c4ed85cf\tFalse\n# flux-system\tingress-nginx-charts True \tFetched revision: 45669a3117fc93acc09a00e9fb9b4445e8990722\t45669a3117fc93acc09a00e9fb9b4445e8990722\tFalse\n# flux-system\tjetstack-charts      True \tFetched revision: 7bad937cc82a012c9ee7d7a472d7bd66b48dc471\t7bad937cc82a012c9ee7d7a472d7bd66b48dc471\tFalse\n# flux-system\tk8s-at-home-charts   True \tFetched revision: 1b24af9c5a1e3da91618d597f58f46a57c70dc13\t1b24af9c5a1e3da91618d597f58f46a57c70dc13\tFalse\n```\n\nFlux has a wide range of CLI options available be sure to run `flux --help` to view more!\n\n## :robot:\u0026nbsp; Automation\n\n[Renovate](https://www.whitesourcesoftware.com/free-developer-tools/renovate) is a very useful tool that when configured will start to create PRs in your Github repository when Docker images, Helm charts or anything else that can be tracked has a newer version. The configuration for renovate is located [here](./.github/renovate.json5).\n\nThere's a couple Github workflows included in this repository that will help automate some processes.\n\n- [Flux upgrade schedule](./.github/workflows/flux-schedule.yaml) - workflow to upgrade Flux.\n- [Renovate schedule](./.github/workflows/renovate-schedule.yaml) - workflow to annotate `HelmRelease`'s which allows [Renovate](https://www.whitesourcesoftware.com/free-developer-tools/renovate) to track Helm chart versions.\n\n## :grey_question:\u0026nbsp; What's next\n\nThe world is your cluster, try installing another application or if you have a NAS and want storage back by that check out the helm charts for [democratic-csi](https://github.com/democratic-csi/democratic-csi), [csi-driver-nfs](https://github.com/kubernetes-csi/csi-driver-nfs) or [nfs-subdir-external-provisioner](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner).\n\nIf you plan on exposing your ingress to the world from your home. Checkout [our guide](https://docs.k8s-at-home.com/guides/dyndns/) to run a k8s `CronJob` to update DDNS.\n\n## :handshake:\u0026nbsp; Thanks\n\nBig shout out to all the authors and contributors to the projects that we are using in this repository.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fchipwolf%2Fk3s-sops-demo","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fchipwolf%2Fk3s-sops-demo","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fchipwolf%2Fk3s-sops-demo/lists"}