virtink VS cert-manager

$ kubectl apply -f https://github.com/smartxworks/virtink/releases/download/v0.11.0/virtink.yaml  ✔   namespace/virtink-system created customresourcedefinition.apiextensions.k8s.io/virtualmachinemigrations.virt.virtink.smartx.com created customresourcedefinition.apiextensions.k8s.io/virtualmachines.virt.virtink.smartx.com created serviceaccount/virt-controller created serviceaccount/virt-daemon created clusterrole.rbac.authorization.k8s.io/virt-controller created clusterrole.rbac.authorization.k8s.io/virt-daemon created clusterrolebinding.rbac.authorization.k8s.io/virt-controller created clusterrolebinding.rbac.authorization.k8s.io/virt-daemon created service/virt-controller created deployment.apps/virt-controller created daemonset.apps/virt-daemon created certificate.cert-manager.io/virt-controller-cert created certificate.cert-manager.io/virt-daemon-cert created issuer.cert-manager.io/virt-controller-cert-issuer created issuer.cert-manager.io/virt-daemon-cert-issuer created mutatingwebhookconfiguration.admissionregistration.k8s.io/virtink-mutating-webhook-configuration created validatingwebhookconfiguration.admissionregistration.k8s.io/virtink-validating-webhook-configuration created $ kubectl get po,svc -A  ✔  NAMESPACE NAME READY STATUS RESTARTS AGE kube-system pod/local-path-provisioner-7b7dc8d6f5-8cwd8 1/1 Running 0 10m kube-system pod/coredns-b96499967-cc7fw 1/1 Running 0 10m kube-system pod/svclb-traefik-baea9d36-vjxzg 2/2 Running 0 10m kube-system pod/helm-install-traefik-crd-ghbn2 0/1 Completed 0 10m kube-system pod/svclb-traefik-baea9d36-2vw6x 2/2 Running 0 10m kube-system pod/helm-install-traefik-fc9xw 0/1 Completed 1 10m kube-system pod/svclb-traefik-baea9d36-g42x2 2/2 Running 0 10m kube-system pod/traefik-56cfcbb99f-5qgvd 1/1 Running 0 10m kube-system pod/metrics-server-84f8d4c4fc-wx8bl 1/1 Running 0 10m cert-manager pod/cert-manager-cainjector-5987875fc7-g94ft 1/1 Running 0 2m58s cert-manager pod/cert-manager-6dd9658548-slxrp 1/1 Running 0 2m58s cert-manager pod/cert-manager-webhook-7b4c5f579b-76x57 1/1 Running 0 2m58s virtink-system pod/virt-daemon-dv9m9 1/1 Running 0 41s virtink-system pod/virt-daemon-mv994 1/1 Running 0 41s virtink-system pod/virt-controller-768b979d4-gzlzt 1/1 Running 0 41s virtink-system pod/virt-daemon-jpz87 1/1 Running 0 41s NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default service/kubernetes ClusterIP 10.43.0.1 443/TCP 11m kube-system service/kube-dns ClusterIP 10.43.0.10 53/UDP,53/TCP,9153/TCP 11m kube-system service/metrics-server ClusterIP 10.43.21.66 443/TCP 10m kube-system service/traefik LoadBalancer 10.43.170.138 174.138.1.202,188.166.109.175,188.166.88.194 80:32630/TCP,443:30841/TCP 10m cert-manager service/cert-manager ClusterIP 10.43.182.103 9402/TCP 2m59s cert-manager service/cert-manager-webhook ClusterIP 10.43.136.111 443/TCP 2m58s virtink-system service/virt-controller ClusterIP 10.43.196.10 443/TCP 42s

Virtink is a Kubernetes add-on for running Cloud Hypervisor virtual machines. By using Cloud Hypervisor as the underlying hypervisor, Virtink enables a lightweight and secure way to run fully virtualized workloads in a canonical Kubernetes cluster.

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