-
Notifications
You must be signed in to change notification settings - Fork 0
Kubernetes
Michael O'Brien edited this page Sep 5, 2024
·
21 revisions
Rancher 1.6 to 2.0 was the goto bare metal or VM supported kubernetes distribution in the 2017-2019 timeframe around Kubernetes 1.7. The rancher product was integrated into SUSE and continues to support RKE 1 (original) and RKE 2 (FedRAMP compliant). K3s is the edge version of the RKE distribution as a CNCF project.
see - https://github.com/ObrienlabsDev/biometric-backend/issues/11
Limit installations to Ubuntu 22.04+ on IA64 (ARM64 is experimental). As of 202408 the following kubernetes components are supported for v1.30.2
- Kubernetes: v1.30.2
- RKE2 Version: v1.30.2+rke2r1
- Etcd: v3.5.13-k3s1
- Containerd: v1.7.17-k3s1
- Runc: v1.1.12
- Metrics-server: v0.7.1
- CoreDNS: v1.11.1
- Ingress-Nginx: v1.10.1-hardened1
- Helm-controller: v0.16.1
- CNI: Canal (Flannel: v0.25.4, Calico: v3.28.0)
- CNI: Calico v3.27.3
- CNI: Cilium v1.15.5
- CNI: Multus v4.0.2
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
sudo install minikube-linux-amd64 /usr/local/bin/minikube && rm minikube-linux-amd64
minikube start
Enable kubernetes 1.29
For
ichaelobrien@mbp7 kubernetes % kubectl get nodes
E0802 19:52:50.751864 60075 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:64151/api?timeout=32s": dial tcp 127.0.0.1:64151: connect: connection refused
The connection to the server 127.0.0.1:64151 was refused - did you specify the right host or port?
If previously running "kind" switch to docker desktop
michaelobrien@mbp7 kubernetes % kubectl get nodes
NAME STATUS ROLES AGE VERSION
docker-desktop Ready control-plane 4m18s v1.29.2
- Latest 4.12
- https://www.redhat.com/en/services/training/do080-deploying-containerized-applications-technical-overview
- https://www.redhat.com/en/services/training/red-hat-openshift-administration-i-operating-a-production-cluster
- https://www.redhat.com/en/services/training/do281-red-hat-openshift-administration-ii-configuring-a-production-cluster-with-exam