You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I gather from the docs, that the standard pattern to create a client is with KubeConfig's makeApiClient (see here ).
However, there is no way to create a client with middlewares.
My use case is to add a proxy or use impersonation headers to a client, that was possible in the client's instance with apiclient.addInterceptor and it seem the new mechanism is using middlewares.
What would be the best place to give a middleware?
Should it be an argument to the makeApiClientfactory or is it better to make them part of the kube config, eg, config.addMiddlewares?
I feel inclined towards the first option, but I'm relatively new to this library.
The text was updated successfully, but these errors were encountered:
I gather from the docs, that the standard pattern to create a client is with
KubeConfig
'smakeApiClient
(see here ).However, there is no way to create a client with middlewares.
My use case is to add a proxy or use impersonation headers to a client, that was possible in the client's instance with
apiclient.addInterceptor
and it seem the new mechanism is using middlewares.What would be the best place to give a middleware?
Should it be an argument to the
makeApiClient
factory or is it better to make them part of the kube config, eg,config.addMiddlewares
?I feel inclined towards the first option, but I'm relatively new to this library.
The text was updated successfully, but these errors were encountered: