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
fix(backend): honour kubeconfig CA under Bun's native fetch
- Add `BunTlsHttpLibrary` and a `makeApiClient` helper in
`kubeconfig.ts`. The SDK's default `IsomorphicFetchHttpLibrary`
passes the kubeconfig CA via a Node.js `https.Agent`, which Bun's
native `fetch` ignores — it only honours TLS material on the
per-request `tls` option. This caused
`UNABLE_TO_VERIFY_LEAF_SIGNATURE` on every request to clusters with
a private CA (e.g. AKS). The subclass re-injects
`ca`/`cert`/`key`/`rejectUnauthorized` via `tls`; auth headers are
still applied upstream via `authMethods`.
- Route all client construction in `kubernetes.ts`, `auth.ts`,
`autoscaler.ts`, `config.ts`, `registry.ts`, and `secrets.ts`
through `makeApiClient(...)` instead of `kc.makeApiClient(...)`,
making the helper the single source of truth for Bun-safe TLS.
Signed-off-by: Suraj Deshmukh <suraj.deshmukh@microsoft.com>
0 commit comments