Kubernetes Deployments are visible in Discovery payloads but are not created or updated in the CMDB.Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Kubernetes Deployments are missing from the CMDB despite appearing in discovery payloads. Error logs indicate failures in Kubernetes API calls, including 'Received null response for GET call of URL: https://api.target.address:6443/api/v1/namespaces' and 'Method failed: (/api/v1/namespaces/kube-system/endpoints/kube-controller-manager) with code: 404'. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Kubernetes Discovery runs complete but some or all Deployments are missing from the cmdb_ci_kubernetes_deployment table.Deployments appear in ECC Queue payloads but do not result in CI creation.Discovery logs show: Kubernetes Namespace API call failed Received null response for GET call of URL Horizontal Discovery Log shows failures when calling: /api/v1/namespaces MID Server agent.log contains errors such as: ConnectTimeoutException Received null response for GET call SSL or certificate-related warningsERROR (Worker-Interactive:HorizontalDiscoveryProbe-7a74c1c5c3b2bed051bd391a0501310d) [RhinoExceptions:86] com.snc.sw.exception.CommandFailureException: Received null response for GET call of URL: https://api.target.address:6443/api/v1/namespaces .Please check the mid server logs for exact error. Most probable cause is SSL exceptions /certificate exception/ configured URL. (ad_hoc:EvalClosure-get namespaces--1078663688; line 17)org.mozilla.javascript.JavaScriptException: com.snc.sw.exception.CommandFailureException: Received null response for GET call of URL: https://api.target.address:6443/api/v1/namespaces .Please check the mid server logs for exact error. Most probable cause is SSL exceptions /certificate exception/ configured URL. (ad_hoc:EvalClosure-get namespaces--1078663688; line 17)at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1200) Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue observed on Zurich. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The issue is caused by a failed SSL/TLS handshake between the MID Server and the Kubernetes API server. Although the Kubernetes API URL is correct and accessible externally, the MID Server cannot establish a trusted HTTPS connection due to missing or untrusted SSL certificates. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Customer need to contact their internal Kubernetes team to verify SSL certificates and import them into the MID Server. Refer to the documentation for adding SSL certificates.2. Perform a Pattern Sync to MID after importing certificates to ensure changes are applied.3. Re-check credentials and permissions for the discovery schedule to ensure they are correctly configured.4. Conduct a Postman test from the MID Server to validate connectivity to Kubernetes URLs, coordinating with the Kubernetes team on API requests: How to test AWS REST API using POSTMAN