korifi VS kind

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

To get started, you'll need to install clusteradm and kubectl and start up three Kubernetes clusters. To simplify cluster administration, this article starts up three kind clusters with the following names and purposes:

Kind: is a tool for running local Kubernetes clusters using Docker container "nodes." It was primarily designed for testing Kubernetes itself but can also be used for local development or continuous integration.

Fortunately, just as projects like kind and Minikube enable developers to spin up a local Kubernetes environment in no time, CRC, also known as OpenShift Local and a recursive acronym for "CRC - Runs Containers", offers developers a local OpenShift environment by means of a pre-configured VM similar to how Minikube works under the hood.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Features compared to https://kind.sigs.k8s.io/

Kind allows you to run a Kubernetes cluster inside Docker. This is incredibly useful for developing Helm charts, Operators, or even just testing out different k8s features in a safe way.

Check out KinD

If you're just messing around, just use kind (https://kind.sigs.k8s.io) or minikube if you want VMs (https://minikube.sigs.k8s.io). Both work on ARM-based platforms.

You can also use k3s; it's hella easy to get started with and it works great.

We'll install APIClarity into a Kubernetes cluster to test our API documentation. We're using a Kind cluster for demonstration purposes. Of course, if you have another Kubernetes cluster up and running elsewhere, all steps also work there.

yes I know there is lens, but it does not allow me to see logs of multiple pods at same time and what is even more important it is not friendly for ephemeral clusters - in my case with help of kind I am recreating whole cluster each time from scratch