Kubernetes Discovery completes successfully without discovering the Nodes with pattern steps error: Invalid username/password comboIssue After running serverless Kubernetes horizontal discovery the discover ended successfully for Cluster, Namespaces and Pods but not for Nodes.No new records will be added to [cmdb_ci_kubernetes_node]. Identify if the credentials or credentials alias used for discovery are correct Identify if the MID Server used for discovery is having the proper rights The following API's are in the scope of discovery: https://<url>/api/v1/namespaces/ https://<url>/api/v1/namespaces/<namespace> https://<url>/api/v1/namespaces/kube-system/endpoints/kube-controller-manager https://<url>/api/v1/services https://<url>/api/v1/pods https://<url>/api/v1/nodes If the last discovery activity performed against this Kubernetes Cluster is available then the payload from DISCOVERY will have: https://<instance>.service-now.com/$sw_horizontal_discovery_log.do?discoLogId=ff749bf38734b490e7614157cebb35fa&saDiscoLogSysId=b7749bf38734b490e7614157cebb35fa&ipAddress=No%20Source&pid=&preExecution=ewogICJjcmVkZW50aWFsc0FsaWFzIiA6ICJzdmNfazhzX2FudGhvc19kZXYwMSIsCiAgInByb21ldGhldXNVUkwiIDogIiIsCiAgIm5hbWVzcGFjZSIgOiAia3ViZS1zeXN0ZW0iLAogICJ1cmwiIDogImh0dHBzOi8vMTAuOTEuMjMyLjE1OjQ0MyIKfQ==&host_sys_id=&host_name=&patternId=96324ec09f3303002ae692ec757fcf61&patternName=Kubernetes&patternType=3&isCloud=false&isHistoricalLog=true - Expand Discovery Log -> Identification - Click on "get nodes" and observe the output: "2021-06-24 15:24:27: Pattern HTTP GET to https://10.XX.YYY.ZZZ:443/api/v1/nodes?limit=50 2021-06-24 15:24:27: Response has error. Status code is 403 . error code: 6 . error message: Method failed: (/api/v1/nodes) with code: 403 - Forbidden username/password combo 2021-06-24 15:24:27: HTTP response: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"nodes is forbidden: User \"system:serviceaccount:default:svc-k8s-discovery\" cannot list resource \"nodes\" in API group \"\" at the cluster scope","reason":"Forbidden","details":{"kind":"nodes"},"code":403} " If the payload is not available a debug of the pattern will need to be executed. At the step 15 the output will contain a message like: {"kind":"Status", "apiVersion":"v1", "metadata":{}, "status":"Failure", "message":"nodes is forbidden: User \"system:serviceaccount:default:svc-k8s-discovery\" cannot list resource \"nodes\" in API group \"\" at the cluster scope", "reason":"Forbidden", "details":{"kind":"nodes"}, "code":403} ReleaseAllCauseMissing proper permissions to get the Nodes will raise an exception with message: User "system:serviceaccount:default:svc-k8s-discovery" cannot list resource "nodes" .ResolutionReview the Kubernetes Discovery landing page: https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/service-mapping/concept/kubernetes-discovery.htmlIdentify the required permissions for the user performing discovery for the following /api/v1 elements: https://<URL>/api/v1/namespaces/ https://<URL>/api/v1/namespaces/ https://<URL>/api/v1/namespaces/kube-system/endpoints/kube-controller-manager https://<URL>/api/v1/services https://<URL>/api/v1/pods https://<URL>/api/v1/nodes"Validate the permissions using Postman and the credentials defined as Kubernetes Credentials.