Kubernetes

Getting started with containers is fairly easy. This post is just a summary of the steps I took to create a docker container image that I will be using in my kubernetes labs. TLDR Create a free account on hub.docker.com Install Docker Create a Dockerfile. Build an image with the Dockerfile. Run a container with the image you created and perform tests. Push the image to docker hub. Step 01: Install Docker Installation is pretty straight forward....

To troubleshoot calico network issues within guest clusters, debug logging is indispensable. In this post, lets look at the steps that are required to enable debug logging for Calico. We need to first scale down the tkg-controller-manager on the supervisor cluster as we do not want changes we make to the calico pods to be reset. STEP 1: Scale down the tkg-controller-manager From the vCenter Server, login to the control plane VM....

There are two CNIs that are avaiable for container networking in Tanzu kubernetes guest clusters: Antrea and Calico In this post, lets take a closer look at Calico and how to deploy and use Calicoctl Pods can fail if they do not get an ip address from the CNI. A common error is: k get events 4m31s Warning FailedCreatePodSandBox pod/validationservice-59cbc867c-pt7k5 (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "2c0a340dfe947ad27564e0b73d5efac7f13951a77aa9c0a6e5e5d90b7d299e4c": rate: Wait(n=1) would exceed context deadline 4m31s Warning FailedCreatePodSandBox pod/validationservice-59cbc867c-qhdjr (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c0f9ecf1f5a73954bbc3733ff1342fec6896d339bc6039473765e5f143b7850d": rate: Wait(n=1) would exceed context deadline To view the ip blocks provided by IPAM(Calico) in the Tanzu Kubernetes cluster...

Creating a Tanzu Kubernetes Cluster fails. In vCenter server, the resource pool gets created under the namespace resource pool. However, the control/worker vms do not get created. The OVF deployment starts but fails and is in a constant loop with the error, “Failed to deploy OVF package” Looking at the vpxd logs in vCenter Server, the error was: info vpxd[63733] [Originator@6876 sub=Default opID=62236dfd] [VpxLRO] -- ERROR lro-43350730 -- task-637327 -- vim....

If you run into any issue where the config status is stuck in “configuring” state, one of the first things to check is the wcpsvc logs on the vCenter appliance here: /var/log/vmware/wcp/wcpsvc.log Interestingly I ran into an issue where the logs were complaining about authorization. You probably will see the following events in a loop: 2021-05-30T11:48:11.077Z error wcp [kubelifecycle/spherelet.go:923] [opID=domain-c8-host-28] **Failed to get Kubernetes cluster node list: Unauthorized** 2021-05-30T11:48:11.078Z error wcp [kubelifecycle/node\_controller....