Kubernetes Engine Cluster Manager API: Node.js Client

release level npm version codecov

Node.js idiomatic client for Kubernetes Engine cluster management.

Kubernetes Engine is used for building and managing container based applications, powered by the open source Kubernetes technology.

A comprehensive list of changes in each version may be found in the CHANGELOG.

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:


Before you begin

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the Kubernetes Engine Cluster Manager API API.
  4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/container

Using the client library

const container = require('@google-cloud/container');

// Create the Cluster Manager Client
const client = new container.v1.ClusterManagerClient();

async function quickstart() {
  const zone = 'us-central1-a';
  const projectId = await client.getProjectId();
  const request = {
    projectId: projectId,
    zone: zone,

  const [response] = await client.listClusters(request);

Relationship to Kubernetes

@google-cloud/container provides a high level API for creating and managing Google Kubernetes Engine clusters on Google Cloud.

To run commands against the clusters created, you will need to use the Kubernetes API (and the associated kubectl command-line interface).


Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

SampleSource CodeTry it
Quickstartsource codeOpen in Cloud Shell

The Kubernetes Engine Cluster Manager API Node.js Client API Reference documentation also contains samples.

Supported Node.js Versions

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js.

Client libraries targeting some end-of-life versions of Node.js are available, and can be installed via npm dist-tags. The dist-tags follow the naming convention legacy-(version).

Legacy Node.js versions are supported as a best effort:

  • Legacy versions will not be tested in continuous integration.
  • Some security patches may not be able to be backported.
  • Dependencies will not be kept up-to-date, and features will not be backported.

Legacy tags available

  • legacy-8: install client libraries from this dist-tag for versions compatible with Node.js 8.


This library follows Semantic Versioning.

This library is considered to be General Availability (GA). This means it is stable; the code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against GA libraries are addressed with the highest priority.

More Information: Google Cloud Platform Launch Stages


Contributions welcome! See the Contributing Guide.

Please note that this README.md, the samples/README.md, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its template in this directory.


Apache Version 2.0