Whilst working with vRA to deploy various Kubernetes clusters and then register them with Tanzu Mission Control (TMC), I decided to use Postman (a great API Explorer tool) to catalogue my work and build out several use cases.
I’ve posted this here:
This collection was created from the TMC API Documentation. This API is version “v1alpha1” and should be treated as such.
So far, I’ve created the following areas/use cases:
- Attach Cluster
- List Cluster/s
- Cluster Group/s management
- Data Protection management
- Cluster Inspections
I have opted to create the variables inside the collection itself, rather than a separate environment.
Some of the API requests have tests associated, which will populate your variables for you.
You will need your TMC URL and a VMware CSP API Token as your starting point.
Where the requests require some changes in the body that is best not to have as a variable, such as naming a backup, I’ve also tried to add information on the documentation.
Under the Login folder, run “Get Access Token”, which will connect to your TMC URL and use the CSP Refresh Token to generate an Access Token, this access token will be committed to a variable called “accessToken” for use with the other requests.
You will also probably want to run the “Get Organisation ID” as some of the requests require your Org ID, so this will commit it to a variable. This is gathered by looking at the details for your given CSP Token.
If you are running the API to attach a new cluster. Then you will want to run the second request “Get TMC Agent Installer information” which will give you the Installer Link to run in your Kubernetes environment. This data will be written to a variable.
For most of the request that List information, you can use the query “?searchScope.name=” with the API call to filter for necessary objects, or you can use the wildcard value *. I’ve added most of the search filters and value formatters to the requests.
To get the full details for a particular named cluster, I have written the queries for specified clusters, this requires you to provide the management cluster and provisioner of that specified cluster in the query. Essentially it returns the same information as the “Get Clusters List” combined with the SearchScope filter.
So, I won’t describe every set of requests I’ve created. I’ve tried to create these with the bare minimum information you need especially for the POST methods.
If you want to explore the APIs more, you can download an import the Swagger/Open API spec from VMware yourself and import into Postman, but personally I found this hard to work with, and the example bodies give you everything including the responses you won’t need for a POST.
If you’d like to contribute, please do this via the GitHub link!
Looking for more resources around TMC? Then you can check out my other blogs!
Tanzu Mission Control - [Getting Started Tanzu Mission Control](https://vEducate.co.uk/vmware-tanzu-mission-control-getting-started) - [Cluster Inspections](https://vEducate.co.uk/vmware-tanzu-mission-control-cluster-inspections) - [Workspaces and Policies](https://veducate.co.uk/vmware-tanzu-mission-control-workspaces-and-policies/) - [Data Protection](https://veducate.co.uk/?p=3429&preview=true) - [Deploying TKG clusters to AWS](https://veducate.co.uk/tmc-deploy-tkg-aws/) - [Upgrading a provisioned cluster](https://veducate.co.uk/tanzu-mission-control-upgrade-cluster/) - [Delete a provisioned cluster](https://veducate.co.uk/tanzu-mission-control-delete-provisioned-cluster/) - [TKG Management support and provisioning new clusters](https://veducate.co.uk/tmc-tkg-management-provisioning/)
The post Postman Collection for Tanzu Mission Control REST APIs appeared first on vEducate.co.uk.