cert-manager VS democratic-csi

cert-manager

The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.

On top of its core components, SpinKube depends on cert-manager. cert-Manager is responsible for provisioning and managing TLS certificates that are used by the admission webhook system of the Spin Operator. Let’s install cert-manager and KWasm using the commands shown here:

terraform { required_providers { kubectl = { source = "gavinbunney/kubectl" version = "1.14.0" } } } # The reference to the current project or a AWS project data "google_client_config" "provider" {} # The reference to the current cluster or EKS data "google_container_cluster" "my_cluster" { name = var.cluster_name location = var.cluster_location } # We configure the kubectl provider to use those values for authenticating provider "kubectl" { host = data.google_container_cluster.my_cluster.endpoint token = data.google_client_config.provider.access_token cluster_ca_certificate = base64decode(data.google_container_cluster.my_cluster.master_auth[0].cluster_ca_certificate) } #Download the multiple manifests file. data "http" "cert_manager_crds" { url = "https://github.com/cert-manager/cert-manager/releases/download/v${var.cert_manager_version}/cert-manager.crds.yaml" } data "kubectl_file_documents" "cert_manager_crds" { content = data.http.cert_manager_crds.response_body lifecycle { precondition { condition = 200 == data.http.cert_manager_crds.status_code error_message = "Status code invalid" } } } # We use the for_each or else this kubectl_manifest will only import the first manifest in the file. resource "kubectl_manifest" "cert_manager_crds" { for_each = data.kubectl_file_documents.cert_manager_crds.manifests yaml_body = each.value }

SSL certificates thanks to Cloudflare and cert-manager

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/${CERT_MANAGER_VERSION}/cert-manager.crds.yaml

put the Sub-CA inside hashicorp vault to be used for automatic signing of services like https://cert-manager.io/ inside our k8s clusters.

install-cert-manager: desc: Install cert-manager deps: - init-cluster cmds: - kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/{{.CERT_MANAGER_VERSION}}/cert-manager.yaml - echo "Waiting for cert-manager to be ready" && sleep 25 status: - kubectl -n cert-manager get pods | grep Running | wc -l | grep -q 3

I've been pretty frustrated with how private CAs are supported. Your private root CA can be maliciously used to MITM every domain on the Internet, even though you intend to use it for only a couple domain names. Most people forget to set Name Constraints when they create these and many helper tools lack support [1][2]. Worse, browser support for Name Constraints has been slow [3] and support isn't well tracked [4]. Public CAs give you certificate transparency and you can subscribe to events to detect mis-issuance. Some hosted private CAs like AWS's offer logs [5], but DIY setups don't.

Even still, there are a lot of folks happily using private CAs, they aren't the target audience for this initial release.

[1] https://github.com/FiloSottile/mkcert/issues/302

[2] https://github.com/cert-manager/cert-manager/issues/3655

[3] https://alexsci.com/blog/name-non-constraint/

[4] https://github.com/Netflix/bettertls/issues/19

[5] https://docs.aws.amazon.com/privateca/latest/userguide/secur...

the Cert Manager

The interface software regarding is not a worry of mine, as democratic-csi does the storage management for me, thus the compatibility it is not limited to the application using the storage per se, as this is handled by Kubernete's CSI drivers, being application-agnostic when utilizing the storage provided.My main worry is not latency, but rather RAM

Check out https://github.com/democratic-csi/democratic-csi

in k3s, i'm using https://github.com/democratic-csi/democratic-csi (was using iSCSI before, now everything is NFS)

Have you checked this out? GitHub democratic-csi I have yet to test this in my @home K8s cluster. It supports iSCSI volume management for FreeNAS, Synology and other CSI backends.

If you ever migrate from docker up to kubernetes, then take a look into democratic-csi. For a modest homelab, it is a valid option (said from somebody who manages a small homelab and plays around with kubernetes).

For persistent storage have you looked into using TrueNAS with a CSI provider with your container orchestrator? I'm assuming your orchestrator is Nomad or Kubernetes.

Yes, Rancher does support FreeNAS, TrueNAS. and Scale using the storage class provider https://github.com/democratic-csi/democratic-csi It's important to remember Rancher is the server. And in this case, you need to ask the question does the k8s cluster that Rancher is managing support this storage class provider? If you are using RKE the answer is Yes.

I use https://github.com/democratic-csi/democratic-csi to mount nfs/iscsi shares (and manage the shares) from my SAN (truenas box).

iSCSI with democratic-csi (https://github.com/democratic-csi/democratic-csi) works great for me on truenas. I use iSCSI for any PVs that don't need to be shared and NFS for anything I'd like to share between different pods (like movies, music).

Storage - democratic-csi looked the most promising, it has worked well so far. I am using zfs-generic-iscsi against an Ubuntu 20.04 storage server. I also tried zfs-generic-nfs and it worked successfully with the caveat of having to deal with NFS file permissions.