I am getting an unauthorized error with with the Kubernetes connector. I can login to the Kubernetes dashboard using the same IP:Port and token from the web browser on the DMA as I am using for the DataMiner connector. But I get the following error using both DataMiner connectors versions
1.2.1.1 and 1.2.2.10.
Here is the log file
2022/06/13 03:37:30.543|SLManagedScripting.exe|ManagedInterop|ERR|0|125|QA2|ParseData|Exception: System.Net.WebException: Status: 400|Description: Request|Message : |URI: api/v1/nodes at Extensions.Http.AddOrUpdateResponse(SLProtocol protocol, String status, String response, DataType dataType, String message) at QAction.Run(SLProtocolExt protocol) 2022/06/13 03:37:30.841|SLManagedScripting.exe|ManagedInterop|ERR|0|125|QA2|ParseData|Exception: System.Net.WebException: Status: 400|Description: Request|Message : |URI: api/v1/namespaces at Extensions.Http.AddOrUpdateResponse(SLProtocol protocol, String status, String response, DataType dataType, String message) at QAction.Run(SLProtocolExt protocol)
When the cluster is back up and running you could test through Postman. If I am correct these are the calls that the protocol is trying to do:
- GET /api/v1/nodes
- GET /api/v1/namespaces
You can find the API definition for the Kubernetes API here.
Hi Randy,
A 400 Bad Request means the request cannot be handled by the server, which in this case does not mean there is something wrong with the authorization.
I’m no expert on the Kubernetes integration and this issue could be caused by a lot of things (requests could for example target a different API). Have you verified the requests sent from the element using a standalone tool like Postman for example?
Thanks for the help. The lab had to shut down the kubernetes because of some lab resource issues so I was not able to test further.