Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
@google-cloud/container
Advanced tools
@google-cloud/container is a Node.js client library for Google Kubernetes Engine (GKE). It allows developers to interact with GKE clusters programmatically, enabling operations such as creating, managing, and deleting clusters, as well as retrieving information about clusters and their nodes.
Create a Cluster
This feature allows you to create a new Kubernetes cluster in GKE. The code sample demonstrates how to use the @google-cloud/container package to create a cluster with a specified name, initial node count, and node configuration.
const {ClusterManagerClient} = require('@google-cloud/container');
const client = new ClusterManagerClient();
async function createCluster() {
const request = {
parent: 'projects/YOUR_PROJECT_ID/locations/YOUR_LOCATION',
cluster: {
name: 'my-cluster',
initialNodeCount: 3,
nodeConfig: {
machineType: 'n1-standard-1'
}
}
};
const [operation] = await client.createCluster(request);
console.log('Cluster creation operation:', operation);
}
createCluster().catch(console.error);
List Clusters
This feature allows you to list all the Kubernetes clusters in a specified project and location. The code sample demonstrates how to use the @google-cloud/container package to retrieve and print the list of clusters.
const {ClusterManagerClient} = require('@google-cloud/container');
const client = new ClusterManagerClient();
async function listClusters() {
const request = {
parent: 'projects/YOUR_PROJECT_ID/locations/YOUR_LOCATION'
};
const [response] = await client.listClusters(request);
console.log('Clusters:', response.clusters);
}
listClusters().catch(console.error);
Delete a Cluster
This feature allows you to delete an existing Kubernetes cluster in GKE. The code sample demonstrates how to use the @google-cloud/container package to delete a cluster by specifying its name.
const {ClusterManagerClient} = require('@google-cloud/container');
const client = new ClusterManagerClient();
async function deleteCluster() {
const request = {
name: 'projects/YOUR_PROJECT_ID/locations/YOUR_LOCATION/clusters/YOUR_CLUSTER_NAME'
};
const [operation] = await client.deleteCluster(request);
console.log('Cluster deletion operation:', operation);
}
deleteCluster().catch(console.error);
The kubernetes-client package is a Node.js client for the Kubernetes API. It provides a way to interact with Kubernetes clusters, including creating, updating, and deleting resources such as pods, services, and deployments. Compared to @google-cloud/container, kubernetes-client is more general-purpose and can be used with any Kubernetes cluster, not just GKE.
The k8s package is another Node.js client for the Kubernetes API. It offers a simple and flexible way to manage Kubernetes resources programmatically. Like kubernetes-client, it is not specific to GKE and can be used with any Kubernetes cluster. It provides similar functionalities to @google-cloud/container but with a broader scope.
Google Container Engine API client for Node.js
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:
npm install @google-cloud/container
async function main() {
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);
console.log('Clusters: ', response);
}
quickstart();
}
main().catch(console.error);
Samples are in the samples/
directory. Each sample's README.md
has instructions for running its sample.
Sample | Source Code | Try it |
---|---|---|
Cluster_manager.cancel_operation | source code | |
Cluster_manager.check_autopilot_compatibility | source code | |
Cluster_manager.complete_i_p_rotation | source code | |
Cluster_manager.complete_node_pool_upgrade | source code | |
Cluster_manager.create_cluster | source code | |
Cluster_manager.create_node_pool | source code | |
Cluster_manager.delete_cluster | source code | |
Cluster_manager.delete_node_pool | source code | |
Cluster_manager.get_cluster | source code | |
Cluster_manager.get_j_s_o_n_web_keys | source code | |
Cluster_manager.get_node_pool | source code | |
Cluster_manager.get_operation | source code | |
Cluster_manager.get_server_config | source code | |
Cluster_manager.list_clusters | source code | |
Cluster_manager.list_node_pools | source code | |
Cluster_manager.list_operations | source code | |
Cluster_manager.list_usable_subnetworks | source code | |
Cluster_manager.rollback_node_pool_upgrade | source code | |
Cluster_manager.set_addons_config | source code | |
Cluster_manager.set_labels | source code | |
Cluster_manager.set_legacy_abac | source code | |
Cluster_manager.set_locations | source code | |
Cluster_manager.set_logging_service | source code | |
Cluster_manager.set_maintenance_policy | source code | |
Cluster_manager.set_master_auth | source code | |
Cluster_manager.set_monitoring_service | source code | |
Cluster_manager.set_network_policy | source code | |
Cluster_manager.set_node_pool_autoscaling | source code | |
Cluster_manager.set_node_pool_management | source code | |
Cluster_manager.set_node_pool_size | source code | |
Cluster_manager.start_i_p_rotation | source code | |
Cluster_manager.update_cluster | source code | |
Cluster_manager.update_master | source code | |
Cluster_manager.update_node_pool | source code | |
Cluster_manager.cancel_operation | source code | |
Cluster_manager.check_autopilot_compatibility | source code | |
Cluster_manager.complete_i_p_rotation | source code | |
Cluster_manager.complete_node_pool_upgrade | source code | |
Cluster_manager.create_cluster | source code | |
Cluster_manager.create_node_pool | source code | |
Cluster_manager.delete_cluster | source code | |
Cluster_manager.delete_node_pool | source code | |
Cluster_manager.get_cluster | source code | |
Cluster_manager.get_j_s_o_n_web_keys | source code | |
Cluster_manager.get_node_pool | source code | |
Cluster_manager.get_operation | source code | |
Cluster_manager.get_server_config | source code | |
Cluster_manager.list_clusters | source code | |
Cluster_manager.list_locations | source code | |
Cluster_manager.list_node_pools | source code | |
Cluster_manager.list_operations | source code | |
Cluster_manager.list_usable_subnetworks | source code | |
Cluster_manager.rollback_node_pool_upgrade | source code | |
Cluster_manager.set_addons_config | source code | |
Cluster_manager.set_labels | source code | |
Cluster_manager.set_legacy_abac | source code | |
Cluster_manager.set_locations | source code | |
Cluster_manager.set_logging_service | source code | |
Cluster_manager.set_maintenance_policy | source code | |
Cluster_manager.set_master_auth | source code | |
Cluster_manager.set_monitoring_service | source code | |
Cluster_manager.set_network_policy | source code | |
Cluster_manager.set_node_pool_autoscaling | source code | |
Cluster_manager.set_node_pool_management | source code | |
Cluster_manager.set_node_pool_size | source code | |
Cluster_manager.start_i_p_rotation | source code | |
Cluster_manager.update_cluster | source code | |
Cluster_manager.update_master | source code | |
Cluster_manager.update_node_pool | source code | |
Quickstart | source code |
The Kubernetes Engine Cluster Manager API Node.js Client API Reference documentation also contains samples.
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.
Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed through npm dist-tags.
The dist-tags follow the naming convention legacy-(version)
.
For example, npm install @google-cloud/container@legacy-8
installs client libraries
for versions compatible with Node.js 8.
This library follows Semantic Versioning.
This library is considered to be 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 stable 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 templates in
directory.
Apache Version 2.0
See LICENSE
FAQs
Google Container Engine API client for Node.js
The npm package @google-cloud/container receives a total of 0 weekly downloads. As such, @google-cloud/container popularity was classified as not popular.
We found that @google-cloud/container demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.