Overview
I keep trying to find documents and videos that do an installation of Kubernetes along with associated configurations and including ArgoCD for an environment like mine. This index shows the final Kubernetes installation (list of all pods) plus an index of articles I write (with references) to document the support and build process.
Note that I do have other Kubernetes type articles here, this is a start to finish build series of articles. While they’re all dated November 20th, that’s to let you go from one to the next by clicking on ‘next article’ at the bottom. I did include a couple of prior articles and didn’t change the date so you’ll need to return to the index to continue for them.
My environment consists of a vCenter cluster of three Dell R720XD servers. Virtual machines are created with Terraform from templates which already have the OS (CentOS 7 or Rocky Linux 8) and some basic configurations such as my personal account and a service account that specifically permits NOPASSWD access for the Ansible playbooks.
Note that there’s a problem with Podman (docker replacement for Red Hat based systems) and my container network software (CNI) so I went with CentOS 7 for now. With automation, once it’s working I can rebuild everything quickly 🙂
System descriptions will be provided in the individual documents.
Repositories
These are my github sites with my terraform, ansible playbooks, and gitops yaml files used to build and configure Kubernetes.
I will note that the ones on github are copies of my internal gitlab server. A couple of the repos are connected to github to push updates when I update a master branch but most need me to switch to the main branch, git pull, and then git push github to get the updates publicly available, meaning I have to remember to do so.
I do have a separate git repo for configurations and ansible-vault files which are applied after the main software is deployed. For this project, the Llamas website doesn’t have a separate configuration but other repos such as the Ansible and GitOps repos have separate configuration repos.
In this scenario, you’ll use the Terraform scripts to build the Virtual Machines. When all are up and running, you can use Ansible to configure the new VMs.
Next up would be to further initialize the new VMs. The Process is to run the newserver/initialize Ansible playbook and which install more common configurations but also configurations subject to change, so they aren’t in the template.
Finally, I have a suite of scripts used to manage the servers. Extract information for the inventory for example. Run the utility/unixsuite playbook to install the scripts.
When the core playbooks are done, follow the articles to prepare, create, and configure Kubernetes.
Article List
This is a list of the articles for creating the on-prem infrastructure, building a cluster, installing ArgoCD, and ultimately installing the Llamas band website. I also want to install AWX which is the upstream of Red Hat’s Ansible Automation Hub (formerly Ansible Tower). If no link below, then I’m still working on the installation or page.
- Terraform Builds
- Docker Directory
- Load Balancing Kubernetes
- Kubernetes Storage
- Preparing Kubernetes
- Installing Kubernetes
- Kubernetes Metric Server
- Kubernetes Networking
- Persistent Storage
- Pod Schedule Prioritization
- Resource Management
- Ingress Controller
- Continuous Delivery With ArgoCD
- ArgoCD CLI Commands
- GitLab CI/CD Pipeline
- Llamas Band Website – (Continuous Integration)
- Llamas Band and Continuous Delivery
- Llamas Band and Green/Blue Deployments
- Ansible Automation Platform Installation
- Ansible Automation Platform Logging In
- Ansible Automation Platform Preparation
- Ansible Automation Platform Projects
- Ansible Automation Platform Workflows
- Kubernetes Issues
Example Output
NAMESPACE NAME READY STATUS RESTARTS AGE
argocd argocd-application-controller-0 1/1 Running 0 11d
argocd argocd-applicationset-controller-6c64d9f677-rrd5l 1/1 Running 0 11d
argocd argocd-dex-server-57c6485f6f-5gswb 1/1 Running 0 11d
argocd argocd-notifications-controller-6cc686cd6f-lw8q4 1/1 Running 0 11d
argocd argocd-redis-679bb4b7bd-kxgzg 1/1 Running 0 11d
argocd argocd-repo-server-645f954984-8zb8x 1/1 Running 0 11d
argocd argocd-server-889549b4-ggx97 1/1 Running 0 11h
calico-apiserver calico-apiserver-6fd86fcb4b-77tld 1/1 Running 1 (11d ago) 11d
calico-apiserver calico-apiserver-6fd86fcb4b-p6bzc 1/1 Running 3 (11d ago) 11d
calico-system calico-kube-controllers-dd6c88556-zhg6b 1/1 Running 0 12d
calico-system calico-node-66fkb 1/1 Running 0 12d
calico-system calico-node-99qs2 1/1 Running 0 12d
calico-system calico-node-dtzgf 1/1 Running 0 12d
calico-system calico-node-ksjpr 1/1 Running 1 12d
calico-system calico-node-lhhrl 1/1 Running 0 12d
calico-system calico-node-w8nmx 1/1 Running 0 12d
calico-system calico-typha-69f9d4d5b4-vp7mp 1/1 Running 0 12d
calico-system calico-typha-69f9d4d5b4-xv5tg 1/1 Running 0 12d
calico-system calico-typha-69f9d4d5b4-z65kn 1/1 Running 0 12d
calico-system csi-node-driver-5czsp 2/2 Running 2 12d
calico-system csi-node-driver-ch746 2/2 Running 0 12d
calico-system csi-node-driver-gg9f4 2/2 Running 0 12d
calico-system csi-node-driver-kwbwp 2/2 Running 0 12d
calico-system csi-node-driver-nh564 2/2 Running 0 12d
calico-system csi-node-driver-rvfd4 2/2 Running 0 12d
default echoserver-6f54957b4d-6qc8n 1/1 Running 0 2d20h
default my-nginx-66689dbf87-jkgjk 1/1 Running 0 3d14h
ingress-controller haproxy-ingress-7bc69b8cc-wq2hc 1/1 Running 0 9d
kube-system coredns-9b6bfc8df-fh4kr 1/1 Running 1 12d
kube-system coredns-9b6bfc8df-sn8dj 1/1 Running 1 12d
kube-system etcd-bldr0cuomkube1.dev.internal.pri 1/1 Running 1 11d
kube-system etcd-bldr0cuomkube2.dev.internal.pri 1/1 Running 0 11d
kube-system etcd-bldr0cuomkube3.dev.internal.pri 1/1 Running 0 11d
kube-system kube-apiserver-bldr0cuomkube1.dev.internal.pri 1/1 Running 1 11d
kube-system kube-apiserver-bldr0cuomkube2.dev.internal.pri 1/1 Running 0 11d
kube-system kube-apiserver-bldr0cuomkube3.dev.internal.pri 1/1 Running 0 11d
kube-system kube-controller-manager-bldr0cuomkube1.dev.internal.pri 1/1 Running 1 11d
kube-system kube-controller-manager-bldr0cuomkube2.dev.internal.pri 1/1 Running 0 11d
kube-system kube-controller-manager-bldr0cuomkube3.dev.internal.pri 1/1 Running 0 11d
kube-system kube-proxy-4mr9m 1/1 Running 1 12d
kube-system kube-proxy-gqrd6 1/1 Running 0 12d
kube-system kube-proxy-kg899 1/1 Running 0 12d
kube-system kube-proxy-nwsw8 1/1 Running 0 12d
kube-system kube-proxy-rm7lg 1/1 Running 0 12d
kube-system kube-proxy-zj4sg 1/1 Running 0 12d
kube-system kube-scheduler-bldr0cuomkube1.dev.internal.pri 1/1 Running 1 11d
kube-system kube-scheduler-bldr0cuomkube2.dev.internal.pri 1/1 Running 0 11d
kube-system kube-scheduler-bldr0cuomkube3.dev.internal.pri 1/1 Running 0 11d
kube-system metrics-server-5597479f8d-lwwbg 1/1 Running 0 11d
llamas llamas-6b44d5cd5d-9v52b 1/1 Running 0 43m
llamas llamas-6b44d5cd5d-cpd2h 1/1 Running 0 42m
llamas llamas-6b44d5cd5d-dw7pq 1/1 Running 0 42m
tigera-operator tigera-operator-7d89d9444-4scfq 1/1 Running 3 (11d ago) 12d