Replacement for the "addInterceptor" Function of the Api Clients

[cesarandr]

Hello everyone,
I was wondering on how the addInterceptor function was replaced in the major version update 0.22.3 to 1.0.0.
Im currently trying to add a timeout to the api clients and haven't found a way to do that.

I found that through the applyToHTTPSOptions I can pass a timeout attribute inside of an options object to the KubeConfig but couldn't find how this works exactly.

Any help would be appreciated!

[mstruebing]

Hey @cesarandr this is unfortunately not yet implemented.
We have an open issue regarding the timeout here: #1613

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten