Some kubernetes action 🙂 I’ve just installed prometheus-grafana monitoring on my kubeadm built k8s cluster. This is the repo i used to do such: https://github.com/giantswarm/prometheus After installing, there was an error getting node metrics. The error: Get http://172.16.20.14:10255/metrics: dial tcp 172.16.20.14:10255: getsockopt: connection refused To fix this, you need to allow kubelet read-only port by spe
So I’ve been using terraform for quite sometime now for building-tearing down my kubernetes cluster. One thing that is missing on the provisioned Virtual Machine are tags which I exclusively use for my backup-schedule retention (Veeam). Quick Introduction on Terraform: Terraform lets you “codify” the desired state of your infrastructure. This is awesome as it can be tracked/ checked-in on your favor
I recently uninstalled NSX-V on my environment to prepare for NSX-T. Unfortunately, I encounter the following error when I try to configure/ install NSX-T: Failed to install software on host. Failed to install software on host. esxidr01.ldc.int : java.rmi.RemoteException: [ProfileValidationError] File path of ‘/etc/vmware/firewall/netCPRuleset.xml’ is claimed by multiple non-overlay VIBs: {‘VMware_b
More than one way to skin a cat. The old adage which basically means there are multiple ways to achieve a goal. This is no different in IT and for creating Kubernetes clusters – there have been multiple ways in standing up a fully functioning cluster. Here are some of the I’ve tried and my experience of doing it: If you want an opinionated way of doing it, go PKS (https://docs.vmware.com/en/VMware-Enterpr