Veeam : How to install Kasten K10 on vSphere with Tanzu

Disaster recovery, backup solutions and recoverability in general, are usually critical requirements to run production workloads, even when running pods and containers on a Kubernetes platform.

Veeam with Kasten can help enterprises overcome data management challenges and confidently run applications on Kubernetes clusters.

This vblog focuses on the integration of Kasten and vSphere with VMware Tanzu:

STEP1: helm repo add kasten https://charts.kasten.io/
STEP2: kubectl create namespace kasten-io
STEP3: kubectl get sc
STEP4: helm install k10 kasten/k10 –namespace=kasten-io –set

VMware : Tips of the week #5

You can SSH to a Tanzu Kubernetes cluster TKC worker node as the vmware-system-user using a private key.

Below are the seven steps to follow: 

  • STEP1: Connect to the supervisor cluster
  • STEP2: Switch context to supervisor cluster
  • STEP3: Get secret from specific namespace when your cluster is created
  • STEP4: View the key for the specific cluster
  • STEP5: The key is Base64 encoded, decode it
  • STEP6: Change the access for  the key 
  • STEP7: Connect to one of the worker node

Enjoy

VMware : How to identify the LEADER SupervisorControPlane in vSphere with Tanzu

In this post, we going to show you how you can connect to the supervisor cluster control plane nodes and identify the Leader for Kubernetes master within VMware vSphere with Tanzu. This is important for certain troubleshooting and analysis tasks.

As you maybe know the supervisor cluster is the Kubernetes cluster that we stand up inside of a vSphere cluster when enabling workload management.

The supervisor cluster like other Kubernetes clusters operates an active-passive multi-master model and only one master

VMware : Tips of the week #4

We want to share with you some concepts, helpful commands, and gotchas that we have come across during the first few days within the Kubernetes world.  

Kubernetes uses a command-line tool called kubectl for running commands against clusters,  you may find yourself frustrated by the time spent typing repetitive commands.

This article will highlight tips used to simplify the usage of kubectl and save you time.

Shell aliases can be used to shorten all shell commands and not just

VMware : AWX Host inventory without UUID

When using the VMware vCenter dynamic inventory, the hostname is imported in the following format ‘name_uuid’. For example: vINCEPTION_56474ba9-b3f0-74cb-9ac4-fc895RTbb14b

If you need to get the hosts hostname instead of hostname_uuid using VMware dynamic inventory in AWX, this video will show you how: 

Enjoy! 

VMware : Using Ansible to update VMware vSphere

In any environment, small or large, it’s always considered best practices to keep a platform up to date especially with all the CVE we have seen recently.

With Update Manager or Lifecycle Manager, ESXi patches shouldn’t be that painful. But planning to patch your environment composed of many hosts, on different vSphere Clusters and vCenters may be a challenge for a sysadmin.

Ansible has by default a lot of VMware modules that can help to automate VMware vSphere tasks and

Nutanix Flow isolation Policy with Terraform

Here we go with another blog post on Nutanix and Terraform. 
If you haven’t checked the first video on how to provision VMs on Nutanix AHV with Terraform, here is the link.

The idea of this post is to quickly show you how Terraform can be leveraged to create software-defined network security policies on AHV with Nutanix Flow. For more information on Nutanix Flow capabilities, please refer to the following link: Nutanix-Flow-datasheet

For this blog post, we are going to

Nutanix and Terraform – VM’s Creation

I am sure you have heard of HashiCorp and Terraform solution.

Basically, Terraform is a tool/framework you can leverage to describe/define what your Infrastructure will look like and manage its provisioning (day 1) and Lifecycle (day2).
The power of Terraform is that the description of your Infrastructure is done by having a set of declarative configuration files that are human-readable, which means you don’t need to be an expert in coding to understand and …

Nutanix and Gitlab – vSphere Cluster creation and AOS configuration

In the previous blog post, we showed you how Gitlab and Nutanix Foundation APIs could be leveraged to create a Nutanix AHV cluster from scratch: https://vinception.fr/nutanix-and-gitlab-foundation-and-cluster-creation/In this post, we are going to use the same components, method and process to:

  • Create a Nutanix Cluster with vSphere as the Hypervisor
  • Configure the Nutanix Cluster (AOS settings): Accept Eula, Configure Pulse, DNS, NTP, LCM, Http Proxy, Timezone, SNMP, SMTP, Containers, Syslog, Licensing, Active Directory, Role Mappings

We still have our Gitlab

Nutanix and Gitlab – Foundation and Cluster Creation

Nutanix has a bunch of APIs that you can leverage to automate different processes and reduce operational time, effort, risks, and improve consistency. In the following example, we will see how GitLab can be used to deploy a new AHV cluster from scratch. 

Our Gitlab Project called “ntnx-automation” is composed of different files:

  • A README file, usually a documention, describing requirements, how to use the solution, etc.
  • A ntnx-scripts folder storing all scripts dedicated to the automation project.