Is it possible to pass HttpClientFactory to KubernetesClinet (IKubernetes implementation) for creating HttpClient?

[sankar1204]

I want to pass my own httpClientFactory to the IKubernetes instance, so is it possible to pass HttpClientFactory while creating instance of IKubernetes ?

As I explored it, sometime in 2019 - 2021 it was allowed to take HttpClient in constructor of Kubernetes, but currently its only taking DelegatingHandler in args. Is there any way that I can pass IhttpclientFactroy now.

If someone knows why HttpClient arg is removed from constructor args please explain, or redirect me to that page.

[tg123]

need to install watcher handler to httpclient

[sankar1204]

can you please direct me to an example where httpClient is passed from outside to KubernetesClient

[tg123]

not support
may i know your scenario?

why do you want your own httpclient

[sankar1204]

I need to

• add some default requestHeaders to the request sent from KubernetesClient
• modify retries on certain failure response codes

[tg123]

inherit kubernetes class and override SendRequest

csharp/src/KubernetesClient.Basic/AbstractKubernetes.cs

Line 104 in e64c372

protected abstract Task<HttpResponseMessage> SendRequest<T>(string relativeUri, HttpMethod method, IReadOnlyDictionary<string, IReadOnlyList<string>> customHeaders, T body, CancellationToken cancellationToken);

[sankar1204]

let me try and get back. thanks

[roblappcoupa]

What happened with this? Why was the Kubernetes constructor that took an HttpClient removed? I need to create new instances of Kubernetes because the underlying file-based configuration changes a lot due to a dynamically generated authentication tokens. Therefore, I need to new up a Kubernetes objects often to ensure updated configuration is captured, but I don't want to create new HttpClient instances every time. I was hoping to control the HttpClient that was passed to the Kubernetes constructor but it was removed.

[roblappcoupa]

Thanks for the link. Do you have any suggestions on the best way to manage the HttpClient instances so they come from HttpClientFactory to avoid socket exhaustion issue from creating too many instances?

[tg123]

any reason to create many instances?

[roblappcoupa]

It has to do with how the authentication is managed between my application and my Kubernetes cluster. My .kube config file looks like this:

users:
- name: arn:aws:eks:us-east-1:myawsaccount:cluster/mycluster
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - --region
      - us-east-1
      - eks
      - get-token
      - --cluster-name
      - mycluster
      - --output
      - json
      command: aws

With this, it's my understanding that a token for the Kubernetes API server is dynamically retrieved and it's only good for 15 minutes. Therefore, I need to create new instances of Kubernetes at least every 15 minutes so that they pick up the updated configuration. So my code basically creates a new Kubernetes instance for each workflow that interacts with the Kubernetes API. I could introduce caching so that it only creates one every 15 minutes which would result in fewer instances, but I wanted to try managing the HttpClient instances through HttpClientFactory instead.

[tg123]

sdk will refresh token when expires, you do not have to create a new instance

[roblappcoupa]

After reading your comment and going through the source code I see that now. This changes things for me, so you can disregard the question as I don't need to control the HttpClient instances as I won't need to create so many instances of Kubernetes once I refactor my code. Thanks for the quick responses and guidance!