Back to articles
4 min read

Deploying Istio on VKS Cluster Using Addon Management

Learn how to deploy Istio service mesh on a VKS cluster using Addon Management. This guide walks through installing, managing, and verifying Istio in a simple and automated way.

December 22, 2025Updated Jun 25, 2026832 words
Deploying Istio on VKS Cluster Using Addon Management

What is Addon Management in VKS?

In simple terms:

Addon Management provides a centralized and automated way to install and maintain common Kubernetes platform components on VKS clusters.

Instead of manually installing these components using Helm or YAML files, Addon Management automates deployment and lifecycle management of VKS Standard Packages.

Benefits include: Simplified installation, Consistent configuration, Easier upgrades of Packages and Better integration with the VKS platform

What is Istio?

Istio is a service mesh platform that helps manage communication between microservices running in Kubernetes.

Provides features such as: Traffic management, Secure service-to-service communication, Observability and monitoring, Fault injection and resiliency.

Instead of modifying application code, Istio manages traffic using sidecar proxies (Envoy) that run alongside application containers.

Prerequisites

Before deploying Istio, ensure the following requirements are met:

  1. Access to the Supervisor cluster and Required Namespace permissions
  2. Addon Management enabled in the environment
  3. Running VKS cluster

In this article we’re using the latest release available at the time, VKr 1.35.0, VKS 3.6.0 and VKS Standard Package v3.6.0+20260211

Step 1 — Login to the Supervisor Cluster

text
[root@vks]# export KUBECTL_VSPHERE_PASSWORD='VKSRocks!23'
[root@vks]# kubectl vsphere login --server=192.168.100.100 -u Administrator@vks.local --insecure-skip-tls-verify

Step 2 — Validate Addon release for Istio package is avaialble

text
[root@vks]# kubectl get addonreleases -A | grep -i istio
NAMESPACE                                 NAME                                      ADDON         AGE
vmware-system-vks-public   istio.kubernetes.vmware.com.1.27.1-vmware.1-vks.1        istio         24d
vmware-system-vks-public   istio.kubernetes.vmware.com.1.27.4-vmware.1-vks.1        istio         24d
vmware-system-vks-public   istio.kubernetes.vmware.com.1.27.5-vmware.1-vks.1        istio         24d
vmware-system-vks-public   istio.kubernetes.vmware.com.1.28.2-vmware.1-vks.1        istio         24d

Step 3 — Access the VKS Cluster

If you are not aware how to deploy VKS Cluster please refer the article VKS Cluster Deployment Guide

Verify VKS Cluster Nodes are Ready and Running fine to deplpoy Istio workloads.

text
[root@vks]# kubectl get secret vks-cluster-kubeconfig -n vks-cluster-namespace -o jsonpath='{.data.value}' | base64 -d > vks-cluster-kubeconfig

[root@vks]# kubectl --kubeconfig vks-cluster-kubeconfig  get nodes -A
NAME                                               STATUS   ROLES           AGE   VERSION
vks-cluster-hsd6b-cz92l                            Ready    control-plane   88m   v1.35.0+vmware.2
vks-cluster-hsd6b-jpjxh                            Ready    control-plane   89m   v1.35.0+vmware.2
vks-cluster-hsd6b-tst6c                            Ready    control-plane   91m   v1.35.0+vmware.2
vks-cluster-photon-worker-node-xhph8-cmf9l-2hk9n   Ready    <none>          90m   v1.35.0+vmware.2
vks-cluster-photon-worker-node-xhph8-cmf9l-gvcsl   Ready    <none>          90m   v1.35.0+vmware.2
vks-cluster-photon-worker-node-xhph8-cmf9l-t667r   Ready    <none>          90m   v1.35.0+vmware.2

Step 4 — Verify Package Repository is Reconciled succeessfully for VKS Cluster

text
[root@vks]# kubectl --kubeconfig vks-cluster-kubeconfig get pkgr -A
NAMESPACE           NAME                AGE   DESCRIPTION           PAUSED
vmware-system-tkg   standard-packages   12h   Reconcile succeeded

Step 5 — Prepare YAML template of Istio AddonInstall Object

Replace the values in the following YAML according to your infrastructure and save the file as istio-addon.yaml.

text
---
apiVersion: addons.kubernetes.vmware.com/v1alpha1
kind: AddonInstall
metadata:
  name: <addon_install_name_of_your_choice>
  namespace: <supervisor_namespace_name>
spec:
  addonRef:
    name: istio
  crossNamespaceSelection: Blocked
  clusters:
    - selector:
        matchLabels:
          cluster.x-k8s.io/cluster-name: <vks_cluster_name>

Step 6 — Configure Istio AddonInstall on Supervisor Namespace where VKS Cluster is deployed

text
[root@vks]# kubectl apply -f istio-addon.yaml                      

addoninstall.addons.kubernetes.vmware.com/istio-addon-install-on-vks-cluster created

Step 7 — Verify Istio Standard Package and System Pods are running fine

text
[root@vks]# kubectl --kubeconfig vks-cluster-kubeconfig get pkgi -A | grep -i istio
NAMESPACE           NAME                                     PACKAGE NAME                                  PACKAGE VERSION              DESCRIPTION           AGE     PAUSED

vmware-system-tkg   vks-cluster-istio                        istio.kubernetes.vmware.com                   1.28.2+vmware.1-vks.1        Reconcile succeeded   8m45s
text
[root@vks]# kubectl --kubeconfig vks-cluster-kubeconfig get pods -n istio-system
NAME                            READY   STATUS    RESTARTS   AGE
istio-cni-node-2hrd6            1/1     Running   0          10m
istio-cni-node-4xmd9            1/1     Running   0          10m
istio-cni-node-fhjjk            1/1     Running   0          10m
istio-cni-node-ngwrd            1/1     Running   0          10m
istio-cni-node-pr288            1/1     Running   0          10m
istio-cni-node-swl26            1/1     Running   0          10m
istio-support-cf94f6697-592fc   1/1     Running   0          10m
istiod-dfccbb646-pgsgr          1/1     Running   0          10m
istiod-dfccbb646-xqb9w          1/1     Running   0          10m

Step 8 - Deploy and Verify the Istio Demo App

we can install the bookinfo sample app from Istio, please refer the attached istio-workload.yaml

text
[root@vks]# kubectl --kubeconfig vks-cluster-kubeconfig apply -f istio_workload.yaml
namespace/istio-workload created
service/details created
serviceaccount/bookinfo-details created
deployment.apps/details-v1 created
service/ratings created
serviceaccount/bookinfo-ratings created
deployment.apps/ratings-v1 created
service/reviews created
serviceaccount/bookinfo-reviews created
deployment.apps/reviews-v1 created
deployment.apps/reviews-v2 created
deployment.apps/reviews-v3 created
service/productpage created
serviceaccount/bookinfo-productpage created
deployment.apps/productpage-v1 created

Verify bookstore app pods are running:

text
[root@vks]# kubectl --kubeconfig vks-cluster-kubeconfig get pods -n istio-workload
NAME                              READY   STATUS    RESTARTS   AGE
details-v1-6cc9f5cc44-pldrn       2/2     Running   0          2m46s
productpage-v1-7f885b46fc-qx5x9   2/2     Running   0          2m45s
ratings-v1-77b8b6df5b-j9db5       2/2     Running   0          2m45s
reviews-v1-fdbf79cd8-4r4jb        2/2     Running   0          2m45s
reviews-v2-674c6d8b4-gq5mr        2/2     Running   0          2m45s
reviews-v3-7b775c7568-p98v2       2/2     Running   0          2m45s

Check the bookstore app is running:

text
[root@vks]# kubectl --kubeconfig vks-cluster-kubeconfig -n istio-workload exec $(kubectl --kubeconfig vks-cluster-kubeconfig get pod -l app=ratings -n istio-workload  -o jsonpath='{.items[0].metadata.name}') -c ratings -- curl -sS productpage:9080/productpage | grep -o "<title>.*</title>"
<title>Simple Bookstore App</title>

Summary

Addon Management simplifies the deployment and lifecycle management of Kubernetes platform components in VKS environments.

By providing centralized control, automatic compatibility checks, and simplified upgrades, it allows platform teams to manage add-ons across clusters more efficiently while reducing operational complexity.

Disclaimer

This blog is for informational and educational purposes only. The configurations, examples, and architectural guidance provided are based on general best practices and publicly available references.

Always validate configurations in a non-production environment before applying them to live systems. Features and integrations may vary depending on the versions of VKS, VKr, LCI, Supervisor and vCenter Server being used. The author is not responsible for any unintended impact caused by the use of this information in production environments.

Contents, and opinions are my own and do not reflect the opinions of my employer.

Attachments (1)

Practice Lab
vks
istio
kubernetes

How did you find this article?

Share:
110 views 0 claps 0 comments

Responses (0)

Sign in to join the conversation.

No responses yet. Be the first to share your thoughts!