
Enter the OpenShift or Kubernetes API Endpoint (2):. For the credential type (1), select Kubernetes or Kubernetes API Bearer Token. 🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by defaultĬheck to see if the cluster is up and running, as follows:įigure 1: Adding the Kubernetes cluster credentials. 🌟 Enabled addons: storage-provisioner, default-storageclass, dashboard ▪ Using image kubernetesui/metrics-scraper:v1.0.8 ▪ Using image kubernetesui/dashboard:v2.6.0 ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5 🔄 Restarting existing docker container for "minikube". 👍 Starting control plane node minikube in cluster minikube ✨ Using the docker driver based on existing profile Use `minikube config defaults kubernetes-version` for details. ❗ Specified Kubernetes version 1.25.7 is newer than the newest supported version: v1.24.3. Make sure you have kubectl and minikube CLI installed before getting started with the Kubernetes cluster.
Automation and orchestration are a rock solid combination that yield more promising results.
For this article, we will use a minikube cluster and Ansible Automation Platform 2.3 and a restricted set of privileges in the cluster to deploy the application in Kubernetes. The minikube cluster is the best single node cluster for a personal POC.
This article demonstrates how to deploy gaming applications in a Kubernetes (K8s) cluster using Red Hat Ansible Automation Platform.