Thet title may sound philosophical but You really need visibility in Your Kubernetes environment especially if you’re a n00b :P
You may skip this if you want just the tech bytes :P
Checking the performances from the vCenter UI was always tricky and mostly a gentle art (I still remember the days of watching esxtop to understand what was going on) but we’ve moved on luckily!!
In this post I’ll describe how to set up monitoring in roughly 15 minutes for your Kubernetes clusters
If You google for “Kubernetes Monitoring” you’ll find an insane number of options but most of them will not be very deep on what is happening at the infrastructure layer.
As a recovering VMware admin I want to know which of my VM that is taking Kubernetes workloads is not performing well so I went straight to vROPs ;)
Installing vRealize Operations 7.0 is as easy as deploying an OVA and then just configure username and password. I am going to use the Small setup VM (2 vCPU, 16 GB of ram) and I have configured it to get data from the vCenter hosting my Pivotal Container Service (PKS) lab:
[This took just a few clicks and a few minutes, mostly waiting for the OVA deploy]
Now on to configure it for the Kubernetes part!!
I am going to use vRealize Operations 7.0 and the latest plugin available because I like fresh stuff (and the installation has changed recently) ;)
So let’s download it from the website (you need to sign up to download it). make sure you are using the latest one (1.2).
To add it to vROPs just go to administration and click on Add:
Now you need to deploy a cAdvisor DaemonSet in the cluster that you want to monitor.
No worries if You don’t know what it is: in essence it’s a pod that will start on every Kubernetes worker that you have and will be able to fetch data to feed to vROPs.
To deploy it have a look at my file here.
My only customization is that I am using an image that comes straight from my Harbor container registry.
So to deploy it just do:
kubectl apply -f vrops-cadvisor.yaml
On your cluster.
To see if it is running:
kubectl get daemonset --all-namespaces
You should see something like this (the fluent-bit one is specific for PKS and has nothing to do with vROPs, we’ll talk about it next time but in essence does great stuff collecting your K8s and apps logs :P ):
You should be set.
Just check with a
kubectl describe daemonset vrops-cadvisor --namespace=kube-system
That the daemon set is running on the right port (or the one that You chose)
[In this screenshot you can see the port on which it is running and if it’s in a deployed status]
Ok the CLI part is DONE, let’s switch back to the GUI :P
Now click on the gearbox and then edit the configuration:
Now we will provide the credentials to get to our K8s cluster to vROPS:
Seems like a lot of stuff but let me break it down for you ;)
For the K8s name it’s super easy if you have PKS you can just do this:
pks clusters pkscluster yourclustername
get the ip and perform an nslookup to check for the right name:
Add an https:// in the front and a :8443 in the back and you’re good
Now select daemonSet in the next field
Input the port (you have that via the kubectl describe command that we used before). In my case this is the default 31194
Now for the login to the K8s cluster.
Click on the green plus sign.
A popup will open, select Token Auth and use admin as credential name.
Now go to your kube config file an extract the token suaully this should require a:
The text that You want is just after the id-token: part
Click on Ok, you may need to accept the certificate (that’s a good sign!!):
and use the test connection button
Now you just need some patience as the collector will fetch the right data.
Go to dashboard -> Kubernetes dashboard and wait
Here are some screenshots for your viewing pleasure (see how the info builds up nicely over time):
It totally seems that I have nodes that are too small, we will fix them at the end of the blogpost ;)
I totally plan to test more monitoring options but this is saving my day: I have already discovered that my nodes may be a little bit small.
Long story short I’ll resize them automatically by using BOSH (as I am using PKS that makes my K8s-life easier):
I just have to go to OpsManager, select my plan:
And then pick one of the many options (bigger than the current one):
As soon as I apply my changes the automation will kick in and install fresh new nodes for my cluster gracefully removing the small ones ;)
There’s a new plugin available on the marketplace (version 1.2.1-12305387):
The procedure for installing and configuring it does not change:
Feel free to reach out to me with your feedback!!