-
Notifications
You must be signed in to change notification settings - Fork 68
/
_tmc.html.md.erb
45 lines (37 loc) · 3.43 KB
/
_tmc.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Tanzu Mission Control integration lets you monitor and manage
Tanzu Kubernetes Grid Integrated Edition clusters from the Tanzu Mission Control console,
which makes the Tanzu Mission Control console a single point of control
for all Kubernetes clusters. For more information about Tanzu Mission Control, the [Tanzu Mission Control documentation](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components.html).
To integrate Tanzu Kubernetes Grid Integrated Edition with Tanzu Mission Control:
1. Confirm that the TKGI API VM has internet access and
can connect to `cna.tmc.tanzu.broadcom.com` and the other outbound URLs listed in
the [What Happens When You Attach a Cluster](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-mission-control/1-4/tanzu-mission-control-documentation/tanzumc-concepts-GUID-147472ED-16BB-4AAA-9C35-A951C5ADA88A.html) section of the Tanzu Mission Control Product
documentation.
1. Navigate to the **Tanzu Kubernetes Grid Integrated Edition** tile > the **Tanzu Mission Control** pane and
select **Yes** under **Tanzu Mission Control Integration**.
<img src="images/tmc-integration.png" alt="Tanzu Mission Control Integration">
1. Configure the fields below:
- **Tanzu Mission Control URL**: Enter the Org URL of your Tanzu Mission Control subscription,
without a trailing slash (`/`). For example, `YOUR-ORG.tmc.tanzu.broadcom.com`.
- **VMware Cloud Services API token**: Enter your API token to authenticate with VMware Cloud Services APIs.
You can retrieve this token by logging in to [VMware Cloud Services](https://console.tanzu.broadcom.com/) and
viewing your account information.
- **Tanzu Mission Control Cluster Group**: Enter the name of a Tanzu Mission Control cluster group.
<br><br>
The name can be `default` or another value, depending on your role and access policy:
- `Org Member` users in VMware cloud services have a `service.admin` role in Tanzu Mission Control.
These users:
- By default, can create and attach clusters only in the `default` cluster group.
- Can create and attach clusters to other cluster groups after an `organization.admin` user grants them the `clustergroup.admin` or `clustergroup.edit` role for those groups.
- `Org Owner` users in VMware cloud services have `organization.admin` permissions in Tanzu Mission Control.
These users:
- Can create cluster groups.
- Can grant `clustergroup` roles to `service.admin` users through the Tanzu Mission Control Access Policy view.
For more information about role and access policy,
see [Access Control](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-mission-control/1-4/tanzu-mission-control-documentation/tanzumc-concepts-GUID-EB9C6D83-1132-444F-8218-F264E43F25BD.html) in the VMware Tanzu Mission Control Product documentation.
<br><br>
- **Tanzu Mission Control Cluster Name Prefix**: Enter a name prefix for identifying the Tanzu Kubernetes Grid Integrated Edition clusters in Tanzu Mission Control.
1. Click **Save**.
<p class="note warning"><strong>Warning:</strong> After the Tanzu Kubernetes Grid Integrated Edition tile is deployed with a configured cluster group, the cluster group cannot be updated.</p>
<p class="note"><strong>Note:</strong> When you upgrade your Kubernetes clusters and have Tanzu Mission Control integration enabled,
existing clusters will be attached to Tanzu Mission Control.</p>