Deploy the Distribution

Deploy the Kubernetes Fury Distribution to a Kubernetes Cluster

This is the easiest part. Be sure you have carefully read the setup section along with all the possible customization options before continuing with the distribution's deployment.

Deploying it

If you have followed all the instructions of the installation section of the guide so far, you are now in conditions of creating all the resources's definitions, that make the Kubernetes Fury Distribution. Let's verify this by executing the following command:

Please note that this command will just print the resources definitions to your screen, it won't create anything on your cluster.

$ kustomize build manifests
# Omitted output

If the previous command succeeds, you are now ready to deploy the resources definitions of the Kubernetes Fury Distribution to your cluster. Let's do that by running the following command:

$ kustomize build manifests | kubectl apply -f -

If the apply command fails at first try after creating some resources, apply it again after a couple of minutes until no error message appears. This is caused by some raceconditions related to custom resource definitions (CRD) registration.

After a while, all the PODs’ status should become “Running”. You can check running the following command:

Tip: you can run the same command using the watch tool to refresh the output every second, like this: watch kubectl get pods -A

$ kubectl get pods -A
NAMESPACE            NAME                                                    READY   STATUS      RESTARTS   AGE
cert-manager         cert-manager-54bb694dc-57kf7                            1/1     Running     0          7m39s
cert-manager         cert-manager-cainjector-898cb7556-2xjxr                 1/1     Running     0          7m39s
cert-manager         cert-manager-webhook-b65959699-7zn59                    1/1     Running     0          7m39s
ingress-nginx        forecastle-744778954f-74kbg                             1/1     Running     0          7m39s
ingress-nginx        nginx-ingress-controller-p2v8z                          1/1     Running     0          7m29s
kube-system          calico-kube-controllers-655bb9f786-nc4xg                1/1     Running     0          7m38s
kube-system          calico-node-cl7rh                                       1/1     Running     0          7m38s
kube-system          calico-node-gzwqz                                       1/1     Running     0          7m38s
kube-system          coredns-5644d7b6d9-9bdtf                                1/1     Running     0          12m
kube-system          coredns-5644d7b6d9-zclqz                                1/1     Running     0          12m
kube-system          etcd-kfd-quick-start-control-plane                      1/1     Running     0          11m
kube-system          kube-apiserver-kfd-quick-start-control-plane            1/1     Running     0          11m
kube-system          kube-controller-manager-kfd-quick-start-control-plane   1/1     Running     0          11m
kube-system          kube-proxy-qjcq6                                        1/1     Running     0          12m
kube-system          kube-proxy-xr4b4                                        1/1     Running     0          12m
kube-system          kube-scheduler-kfd-quick-start-control-plane            1/1     Running     0          11m
kube-system          minio-0                                                 1/1     Running     0          7m38s
kube-system          minio-setup-wjr6v                                       0/1     Completed   0          7m38s
kube-system          velero-79446c99cd-n9fbm                                 1/1     Running     0          7m38s
kube-system          velero-restic-s8ptm                                     1/1     Running     0          7m29s
local-path-storage   local-path-provisioner-7745554f7f-vhgs8                 1/1     Running     0          12m
logging              cerebro-d67c8c48-mm7hb                                  1/1     Running     0          7m38s
logging              elasticsearch-0                                         2/2     Running     0          7m38s
logging              fluentd-jh56j                                           1/1     Running     0          7m38s
logging              fluentd-xvt4z                                           1/1     Running     0          7m38s
logging              kibana-756b6ddfcd-pz2vj                                 1/1     Running     0          7m38s
monitoring           goldpinger-58f54                                        1/1     Running     0          7m38s
monitoring           goldpinger-fzvl2                                        1/1     Running     0          7m38s
monitoring           grafana-864bdcc8d4-hfddg                                1/1     Running     0          7m38s
monitoring           kube-state-metrics-58f8cfc86c-pqxhf                     2/2     Running     0          7m38s
monitoring           node-exporter-kbkmj                                     1/1     Running     0          7m38s
monitoring           node-exporter-xp4x8                                     1/1     Running     0          7m38s
monitoring           prometheus-k8s-0                                        3/3     Running     1          6m49s
monitoring           prometheus-operator-748c7fffd8-8twh7                    1/1     Running     0          7m38s

The output could be slightly different from yours depending of the customization you apply to the kustomize project.

Congratulations! You have now a production grade Kubernetes Cluster thanks to Kubernetes Fury Distribution.