korifi VS cert-manager

ubuntu@korifi:~$ helm install korifi https://github.com/cloudfoundry/korifi/releases/download/v0.5.0/korifi-0.5.0.tgz \ --namespace="$KORIFI_NAMESPACE" \ --set=global.generateIngressCertificates=true \ --set=global.rootNamespace="$ROOT_NAMESPACE" \ --set=adminUserName="$ADMIN_USERNAME" \ --set=api.apiServer.url="api.$BASE_DOMAIN" \ --set=global.defaultAppDomainName="apps.$BASE_DOMAIN" \ --set=global.containerRepositoryPrefix=index.docker.io/mcas/korifi/ \ --set=kpack-image-builder.builderRepository=index.docker.io/mcas//mcas/korifi/kpack-builder NAME: korifi LAST DEPLOYED: Sun Dec 25 19:17:10 2022 NAMESPACE: korifi-system STATUS: deployed REVISION: 1 TEST SUITE: None ubuntu@korifi:~$ helm ls -A NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION korifi korifi-system 1 2022-12-25 19:17:10.041417068 +0000 UTC deployed korifi-0.1.0 dev ubuntu@korifi:~$ kubectl get po,svc -A NAMESPACE NAME READY STATUS RESTARTS AGE cert-manager pod/cert-manager-74d949c895-w6gzm 1/1 Running 0 29m cert-manager pod/cert-manager-cainjector-d9bc5979d-jhr9m 1/1 Running 0 29m cert-manager pod/cert-manager-webhook-84b7ddd796-xw878 1/1 Running 0 29m korifi-system pod/korifi-api-deployment-6b85594bfd-4htmz 1/1 Running 0 97s korifi-system pod/korifi-controllers-controller-manager-58b4d68785-9wfkj 1/1 Running 0 97s korifi-system pod/korifi-job-task-runner-controller-manager-fb844d47-4bwft 1/1 Running 0 97s korifi-system pod/korifi-kpack-build-controller-manager-6cc448db9c-4dw9k 1/1 Running 0 97s korifi-system pod/korifi-statefulset-runner-controller-manager-7cc8fdb476-h6pkd 1/1 Running 0 97s kpack pod/kpack-controller-84cbbcdff6-nnhdn 1/1 Running 0 25m kpack pod/kpack-webhook-56c6b59c4-9zvlb 1/1 Running 0 25m kube-system pod/coredns-565d847f94-kst2l 1/1 Running 0 48m kube-system pod/coredns-565d847f94-rv8pn 1/1 Running 0 48m kube-system pod/etcd-kind-control-plane 1/1 Running 0 48m kube-system pod/kindnet-275pd 1/1 Running 0 48m kube-system pod/kube-apiserver-kind-control-plane 1/1 Running 0 48m kube-system pod/kube-controller-manager-kind-control-plane 1/1 Running 0 48m kube-system pod/kube-proxy-qw9fj 1/1 Running 0 48m kube-system pod/kube-scheduler-kind-control-plane 1/1 Running 0 48m kube-system pod/metrics-server-8ff8f88c6-69t9z 0/1 Running 0 20m local-path-storage pod/local-path-provisioner-684f458cdd-f6zqf 1/1 Running 0 48m metallb-system pod/controller-84d6d4db45-bph5x 1/1 Running 0 45m metallb-system pod/speaker-pcl4p 1/1 Running 0 45m projectcontour pod/contour-7b9b9cdfd6-h5jzg 1/1 Running 0 22m projectcontour pod/contour-7b9b9cdfd6-nhbq2 1/1 Running 0 22m projectcontour pod/contour-certgen-v1.23.2-hxh7k 0/1 Completed 0 22m projectcontour pod/envoy-v4xk9 2/2 Running 0 22m servicebinding-system pod/servicebinding-controller-manager-85f7498cf-xd7jc 2/2 Running 0 18m NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE cert-manager service/cert-manager ClusterIP 10.96.153.49 9402/TCP 29m cert-manager service/cert-manager-webhook ClusterIP 10.96.102.82 443/TCP 29m default service/kubernetes ClusterIP 10.96.0.1 443/TCP 48m korifi-system service/korifi-api-svc ClusterIP 10.96.157.135 443/TCP 97s korifi-system service/korifi-controllers-webhook-service ClusterIP 10.96.106.22 443/TCP 97s korifi-system service/korifi-kpack-build-webhook-service ClusterIP 10.96.202.25 443/TCP 97s korifi-system service/korifi-statefulset-runner-webhook-service ClusterIP 10.96.232.1 443/TCP 97s kpack service/kpack-webhook ClusterIP 10.96.227.201 443/TCP 25m kube-system service/kube-dns ClusterIP 10.96.0.10 53/UDP,53/TCP,9153/TCP 48m kube-system service/metrics-server ClusterIP 10.96.204.62 443/TCP 20m metallb-system service/webhook-service ClusterIP 10.96.186.139 443/TCP 45m projectcontour service/contour ClusterIP 10.96.138.58 8001/TCP 22m projectcontour service/envoy LoadBalancer 10.96.126.44 172.18.255.200 80:30632/TCP,443:30730/TCP 22m servicebinding-system service/servicebinding-controller-manager-metrics-service ClusterIP 10.96.147.189 8443/TCP 18m servicebinding-system service/servicebinding-webhook-service ClusterIP 10.96.14.224 443/TCP 18m

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