npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

k8s.fetch.client

v0.6.0

Published

NodeJS K8s Client using R2 internally for requests.

Downloads

19

Readme

k8s-fetch-client

Kubernetes node client that uses r2 internally for requests to take advantage of fetch and keep the library file size low when running from the browser. The k8s-fetch-client is fully compatible with async/await syntax!

Being written to the Fetch API is a huge benefit for browser users. When running through browserify request is ~2M uncompressed and ~500K compressed. r2 is only 66K uncompressed and 16K compressed.

See https://github.com/mikeal/r2 for more details about r2.

Getting Started

Simply create a new instance of the client and call .connect to parse the given kubernetes cluster's api.

const k8sClient = require('k8s-fetch-client');
const client = new k8sClient({
    host: '0.0.0.0',
    port: '8443'
});

async function start() {
    await client.connect();

    const pods = client.apis.Core.pods.get();
}

start();

How it Works

The .connect function fetches api metadata from the given kubernetes cluster and builds up a series of convenience functions for you to use. All api groups and resources are scoped under client.apis. It determines the preferred API version for each group and then fetches additional information about each Resource in the group. It then builds a series of helpers based on the supported verbs.

Note: Currently the client does not build child resources, e.g. deployments/status will be ignored.

GET /apis/apps/v1beta2

...
{
      "name": "deployments",
      "singularName": "",
      "namespaced": true,
      "kind": "Deployment",
      "verbs": [
        "create",
        "delete",
        "deletecollection",
        "get",
        "list",
        "patch",
        "update",
        "watch"
      ],
      "shortNames": [
        "deploy"
      ],
      "categories": [
        "all"
      ]
    }
},
...

That resource definition will result in the following convenience methods.

verb: create -> client.apis.apps.Deployment.create(payload)
verb: delete -> client.apis.apps.Deployment.delete(identifier)
verb: deleteCollection -> client.apis.apps.Deployment.delete()
verb: get -> client.apis.apps.Deployment.get(identifier)
verb: list -> client.apis.apps.Deployment.get()
verb: patch -> client.apis.apps.Deployment.patch(payload)
verb: update -> client.apis.apps.Deployment.update(payload)
verb: watch -> client.apis.apps.Deployment.watch()

The format is always: client.apis.${resource.name}.${resource.kind}