How to use "exec" with KubernetesClient.Classic? #887
-
Hello, I'm having trouble getting an exec method working with the Classic version of KubernetesClient. I'm using the Classic version because we are using .NET Framework 4.7.2 (and can't upgrade) and also OIDC authentication. I wasn't able to get the standard version working at all with OIDC (using version 4.0.x,, the last version that supports .NET Framework >5). When I switched to the Classic version, our authentication and authorization issues were completely resolved, and we're able to proof of concept every function we are looking for except for exec. I'm finding the following issues: The method in the example (eg. Are there more resources somewhere that I'm not finding? Is exec not supported with Classic? If not, could it be added (and is there reference material to help with doing so)? A sample of the code I'm trying to use is below:
Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
should use |
Beta Was this translation helpful? Give feedback.
ConnectGetNamespacedPodExecAsync
actually return a websocket, the client side shouldupgrade the connection
, that is why you see a badrequest I guessshould use
WebSocketNamespacedPodExecAsync
instead. However, it is not available in net47 because of lacking of websocket APIs.I remember the webocket related APIs were first introduced in netstandard2.1 :(