This PoC test plan and evaluation process focuses on demonstrating functional operation, capabilities, and features of the Tanzu Service Mesh product.
IMPORTANT - This pre-sales offering does not consider all best practices and recommendations for production or extended pilot use. VMware strongly encourages Customers to thoroughly review all publicly available product documentation and engage with the Tanzu Labs, Professional Services Organization, and/or Partners before going forward with any production design decisions. The PoC evaluation system is not the appropriate platform for intensive and lengthy performance testing and evaluation.
This guide is for cloud architects, engineers, administrators, and developers whose organization has an interest integrating Tanzu Service Mesh components and platform into their multi-cloud strategy and environments.
NOTE: BEFORE PROCEEDING TO THE TEST CASES, READ THIS SECTION IN ITS ENTIRETY AS IT INCLUDES PREPARATIONS AND PREREQUISITES REQUIRED TO SUCCESSFULLY RUN THE TEST CASES.
The test cases within this document assume the testing environment and Kubernetes clusters have been provisioned following the Tanzu Service Mesh Environment Requirements and Supported Platforms.
This project contains a Dockerfile
that comes with preconfigured CLIs like kubectl
, tanzu
, kubectl-vshpere
, ... to provide a pre-built and configured environment that makes executing the provided test cases easier (Called here as Local Management Container).To be able to connect with a Kubernetes Cluster copy/download that Kubernetes Cluster's kubeconfig
to a file located in config/kube.conf
inside this project structure (NOTE: This file should NOT be checked into a public source repository). When running the Local Management Container from the supplied make
file the kubeconfig
will be automatically mapped/copied to the running continer and allow for kubectl
commands to your Kubernetes Cluster.
make build
make rebuild
make run
make join
make start
make stop
Test Case ID | Test Case Description |
---|---|
SC01-TC01 | Validate TSM console accessible |
SC01-TC03 | Authorization and API Token |
Test Case ID | Test Case Description |
---|---|
SC02-TC03 | Using TSM REST API |
Test Case ID | Test Case Description |
---|---|
SC03-TC01 | Deploying ACME Fitness Sample Application |
SC03-TC03 | Creating a Global Namespace for a Multi-Cluster ACME Fitness Application Deployment (East/West) |
Test Case ID | Test Case Description |
---|---|
--- | --- |
Test Case ID | Test Case Description |
---|---|
SC05-TC01 | Traffic Management for the Catalog (East/West) service of the ACME Fitness Application |
Test Case ID | Test Case Description |
---|---|
SC06-TC02 | Creates a SLO via the TSM Rest API for the ACME Fitness Application to monitor and capture violations of the SLO during load. |
SC06-TC03 | Creates a Autoscaling Policy via the TSM Rest API for the ACME Fitness Application to trigger up or down scaling events during heavy and light load. |
Test Case ID | Test Case Description |
---|---|
SC07-TC01 | Creates a sample credit card transaction to demonstrate TSM ability to recognize PII data and the service path it traverses. |
SC07-TC02 | Creates a threat detection policy and then generates a sql injection which get captured and displayed as a security event. |