creating a folder and initializing github for our work, then login in to our azure account
creating our environmental variables and checking our Kubernetes version.
creating a resource group in azure with variables
creating Kubernetes in Azure using PowerShell commands. This triggers the creation of a managed Kubernetes control plane and one worker node.
Install aks credentials to my local AKS config path.
Get az aks credentials
List our available nodes and get information on our cluster
Create 2 pods so if a pod fails, we automatically have a replacement for it. we also check the status of the new pods we created
creating load balancers for our pod deployment so that traffic load is shared. This also provides our pods with access to the internet. Pods are usually just internal, but the load balancer provides an external point. It creates a service that exposes a deployment to network traffic; it could make use of either ClusterIP, NodePort, or LoadBalancer.
We can use the following command to monitor our deployment, and as we can see, our deployment now has an IP address. It runs a Kubernetes cluster management command.
Now we can look up our deployment on the internet using the external IP we just got
Our site on the internet transfers data from or to a server—commonly used to test APIs or download files.











Top comments (0)