back to home

kubernetes-client / javascript

JavaScript client

View on GitHub
2,243 stars
564 forks
16 issues

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing kubernetes-client/javascript in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/kubernetes-client/javascript)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Javascript Kubernetes Client information The Javascript clients for Kubernetes is implemented in typescript, but can be called from either Javascript or Typescript. The client is implemented for server-side use with Node. Installation Example code List all pods Create a new namespace Create a cluster configuration programmatically Additional Examples and Documentation There are several more JS and TS examples in the examples directory. Documentation for the library is split into two resources: • The Kubernetes API Reference is the source-of-truth for all Kubernetes client libraries, including this one. We suggest starting here! • The Typedoc autogenerated docs can be viewed online and can also be built locally (see below) Compatibility Prior to the release, release versions did not track Kubernetes versions. Starting with the release, we will increment the minor version whenever we update the minor Kubernetes API version (e.g. ) that this library is generated from. We switched from to as the HTTP(S) backend for the release. Generally speaking newer clients will work with older Kubernetes, but compatibility isn't 100% guaranteed. | client version | older versions | 1.28 | 1.29 | 1.30 | 1.31 | 1.32 | 1.33 | 1.34 | | -------------- | -------------- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | | 0.19.x | - | ✓ | x | x | x | x | x | x | | 0.20.x | - | + | ✓ | x | x | x | x | x | | 0.21.x | - | + | + | ✓ | x | x | x | x | | 0.22.x | - | + | + | + | ✓ | x | x | x | | 1.0.x | - | + | + | + | + | ✓ | x | x | | 1.1.x | - | + | + | + | + | ✓ | x | x | | 1.2.x | - | + | + | + | + | + | ✓ | x | | 1.3.x | - | + | + | + | + | + | ✓ | x | | 1.4.x | - | + | + | + | + | + | + | ✓ | Key: • Exactly the same features / API objects in both javascript-client and the Kubernetes version. • javascript-client has features or api objects that may not be present in the Kubernetes cluster, but everything they have in common will work. • The Kubernetes cluster has features the javascript-client library can't use (additional API objects, etc). • The Kubernetes cluster has no guarantees to support the API client of this version, as it only promises _n_-2 version support. It is not tested, and operations using API versions that have been deprecated and removed in later server versions won't function correctly. Known Issues • Multiple kubeconfigs are not completely supported. Credentials are cached based on the kubeconfig username and these can collide across configs. Here is the related issue. • In scenarios where multiple headers with the same key are required in a request, such as , avoid using . Fetch will merge the values into a single header key, with the values as a single string vs a list of strings, . The workaround is to use a low-level library such as to make the request. Refer to issue #2474 for more details. Contributing Please see CONTRIBUTING.md for development setup, testing, and contribution guidelines.