Kubernetes

Solved1.69K viewsK8S kubernetes
1
0 Comments

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)

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 14th July 2023

2 Answers

1
1.80K 1 Comment

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?

Randy Ulvenes [SLC] [DevOps Advocate] Posted new comment 14th June 2022
Randy Ulvenes [SLC] [DevOps Advocate] commented

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.
You are viewing 1 out of 2 answers, click here to view all answers.