Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

When the "Enable UAA as OIDC provider" checkbox is enabled in Enterprise PKS, the vRealize Operations Solutions Adapter for Containers Monitoring management pack cannot discover and retrieve information from Kubernetes clusters (75169)

Last Updated: 10/16/2019Categories: InformationalTotal Views: 7235Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When the "Enable UAA as OIDC provider" checkbox is enabled in Enterprise PKS, the vRealize Operations Solutions Adapter for Containers Monitoring management pack cannot discover and retrieve information from Kubernetes clusters

Resolution

This is a know issue affecting Enterprise PKS. There is currently no resolution.

Workaround

Implement the following steps to workaround this issue:

Notes: This workaround does not provide a means for automatic discovery and requires manually adding each existing or newly created Kubernetes cluster.  If you delete a Kubernetes cluster, the VI Admin will need to manually delete the respective adapter configuration from vRealize Operations Manager.”

Using a text-editor, create a new file. Paste the following content and modify the ServiceAccount references with a unique value.

apiVersion: v1
kind: ServiceAccount
metadata:
name: vrealize-k8s01
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: vrealize-k8s01
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: vrealize-k8s01
namespace: kube-system

Save and close the file (named rbac-svcacct-vrealize.yaml for this example).

Issue a command similar to the following to create the RBAC policy (creates a service account named “vrealize-k8s01” and a corresponding secret):

kubectl apply -f rbac-svcacct-vrealize.yaml -n kube-system

Issue a command similar to the following to collect the token name for the vrealize service account

kubectl describe sa vrealize-k8s01 -n kube-system

Note: You will see output similar to the following:

Name:                vrealize-k8s01
Namespace:           kube-system
Labels:              <none>
Annotations:         kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{},"name":"vrealize                                                                                -k8s01","namespace":"kube-system"}}
Image pull secrets:  <none>
Mountable secrets:   vrealize-k8s01-token-r94k4
Tokens:              vrealize-k8s01-token-r94k4
Events:              <none>

Issue a command similar to the following to collect the secret token value:

kubectl describe secret vrealize-k8s01-token-r94k4 -n kube-system

Note: You will see output similar to the following:

Name:                vrealize-k8s01
Namespace:           kube-system
Labels:              <none>
Annotations:         kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{},"name":"vrealize                                                                                -k8s01","namespace":"kube-system"}}
Image pull secrets:  <none>
Mountable secrets:   vrealize-k8s01-token-r94k4
Tokens:              vrealize-k8s01-token-r94k4
Events:              <none>
ubuntu@cli-vm:~$ kubectl -n kube-system describe secrets vrealize-k8s01-token-r94k4
Name:         vrealize-k8s01-token-r94k4
Namespace:    kube-system
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: vrealize-k8s01
kubernetes.io/service-account.uid: d3e78716-f027-11e9-8352-005056a54672

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1094 bytes
namespace:  11 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJ2cmVhbGl6ZS1rOHMwMS10b2tlbi1yOTRrNCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJ2cmVhbGl6ZS1rOHMwMSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6ImQzZTc4NzE2LWYwMjctMTFlOS04MzUyLTAwNTA1NmE1NDY3MiIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlLXN5c3RlbTp2cmVhbGl6ZS1rOHMwMSJ9.m1TCOU9L7s36GX7LvjPsNsXausErHtgVNQJLEg1EtyMIYLp6nyVFJTmH6aA-Fk8qpLV98zuiqXeHYISp6g_cFZEd50_uCmIWtEznSnXBAfeJ5YpnOL3thTPYqTmpe_s5n2gyy3wYqc0P3CCl2YNn-cVTxyCoUuLtiEpvIEpExwe2k8Jw6TW8jjmiFJxDpv3yS4ZBJL2IW0Elpue9JiCkigNaxxipuDuEjG0oRrKeTrs4grPMTCOTtTbDaR9LdC8d9q14eSIoWlRAOCpPLzlh43veKjS57amI5o4PCa2AGEIxJVRuQhMgQLa6AFMd3B1EZaCbCOu9NfQDdkMTC2V3mw

Open a web browser and direct it to the vRealize Operations Manager web UI; login with Admin credentials; navigate to Administration > Solutions; select the + icon over the upper table.

When the pop-up window appears, select BROWSE; select the downloaded .pak file; select both checkboxes; select UPLOAD; select NEXT; select the checkbox and NEXT; select FINISH.

In the upper table, highlight the row with the Kubernetes icon then select the gears icon above the table.

Configure the Instance Settings similar to the following:

Display Name: K8S01

Master URL: https://CLUSTER_API_FQDN:8443

Note: Run kubectl cluster-info to collect the URL for this step.

cAdvisor Service: DaemonSet

cAdvisor Port (DaemonSet): 31194

For the Credential, select +; select Token Auth from the Credential Kind drop-down; enter vrealize-k8s01 as the Credential name; paste the TOKEN_VALUE collected in Step 4 in the Bearer Token field; select OK.

Expand Advanced Settings and complete the PKS Cluster ID and vCenter Server parameter.

Note: Collect the cluster-specific PKS Cluster ID by running the pks clusters command.

Select TEST CONNECTION; select ACCEPT; and OK for any other pop-up notices; select SAVE SETTINGS and YES to the pop-up notice; select OK; select CLOSE.

Note: if the adapter won’t connect to the FQDN, replace the FQDN with the IP of the Kubernetes API virtual server.

Navigate to Dashboards > Kubernetes Overview.

Wait 30 minutes for the initial data collection and the dashboard panels to fully populate then refresh the page.

Repeat the previous steps for each existing and newly created Kubernetes cluster.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
利用持有者令牌 - 检索用户信息：包含用户数据的已解码 base64 持有者令牌中存在不一致问题 (75137)

KB
•
在任一节点上重新启动 Docker 服务后，服务不正常，并且部署失败 (75183)

KB
•
ベアラー トークンの利用 - ユーザー情報の取得：ユーザー データを含むデコードされた base64 ベアラー トークンに不整合がある (75137)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant