Skip to content

Commit 001ba22

Browse files
Merge pull request #361 from vmware/bangerar/remove-known-issues
Remove the issue#1 from known issues doc as the cluster class support is available from v1.4.0
2 parents da9cc8e + 5215c85 commit 001ba22

File tree

2 files changed

+2
-30
lines changed

2 files changed

+2
-30
lines changed

docs/guides/known_issues.md

+1-15
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,3 @@
11
# Known Issues in Tanzu Mission Control Provider
22

3-
## Issue #1
4-
- Using Terraform provider to create or modify ClusterClass based clusters running on VMware vSphere v8.x (or above) using Tanzu Mission Control, results in error and failure.
5-
6-
Like below example:
7-
8-
```
9-
Error: Unable to create Tanzu Mission Control cluster entry, name : <cluster-name>: POST request failed with status : 400 Bad Request, response: {"error":"Kubernetes clusters in vSphere 8.0+ must be using ClusterClass, for more information see https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-41DE8F22-56B8-4669-AF3F-E4B4372BDB9E.html","code":9,"message":"Kubernetes clusters in vSphere 8.0+ must be using ClusterClass, for more information see https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-41DE8F22-56B8-4669-AF3F-E4B4372BDB9E.html"}
10-
```
11-
12-
13-
### Workaround
14-
Currently there is no official workaround for using Terraform provider to create ClusterClass based clusters on vSphere 8+ and suggested interim alternate is for using Tanzu Mission Control UI, CLI and/or APIs instead.
15-
16-
### Solution
17-
Native support in the Tanzu Mission Control terraform provider for ClusterClass based K8s clusters running on vSphere 8.x is in development and VMware Tanzu Mission Control will rollout the capability, eliminating the known issue, later in the year.
3+
None

templates/guides/known_issues.md.tmpl

+1-15
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,3 @@
11
# Known Issues in Tanzu Mission Control Provider
22

3-
## Issue #1
4-
- Using Terraform provider to create or modify ClusterClass based clusters running on VMware vSphere v8.x (or above) using Tanzu Mission Control, results in error and failure.
5-
6-
Like below example:
7-
8-
```
9-
Error: Unable to create Tanzu Mission Control cluster entry, name : <cluster-name>: POST request failed with status : 400 Bad Request, response: {"error":"Kubernetes clusters in vSphere 8.0+ must be using ClusterClass, for more information see https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-41DE8F22-56B8-4669-AF3F-E4B4372BDB9E.html","code":9,"message":"Kubernetes clusters in vSphere 8.0+ must be using ClusterClass, for more information see https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-41DE8F22-56B8-4669-AF3F-E4B4372BDB9E.html"}
10-
```
11-
12-
13-
### Workaround
14-
Currently there is no official workaround for using Terraform provider to create ClusterClass based clusters on vSphere 8+ and suggested interim alternate is for using Tanzu Mission Control UI, CLI and/or APIs instead.
15-
16-
### Solution
17-
Native support in the Tanzu Mission Control terraform provider for ClusterClass based K8s clusters running on vSphere 8.x is in development and VMware Tanzu Mission Control will rollout the capability, eliminating the known issue, later in the year.
3+
None

0 commit comments

Comments
 (0)