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

@npm-wharf/cluster-info-client

v2.0.8

Published

secure fetch information about clusters

Downloads

53

Readme

cluster-info-client

A JavaScript API for securely fetching information about groups of clusters.

It stores all cluster information in Vault.

It also manages grouping clusters into "channels". Channels are free-form, and a cluster can be placed into any number of channels. Example uses for channels are deployment groups, environments, zones, or any other grouping of clusters you would want to perform concurrent operations on as a set.

This is intended for use inside fabrik8, support hub, and other cluster automation tooling.

Usage

const createClusterInfoClient = require('@npm_wharf/cluster-info-client')

const client = createClusterInfoClient({
    vaultAddress: process.env.VAULT_ADDR || 'http://localhost:8200',
    vaultToken: process.env.VAULT_TOKEN
})

const clusters = await client.listClusters()

Configuration

|name|description|default value| |---|---|---| |vaultHost|the address, including protocol, to the vault server|'http://localhost:8200'| |vaultRoleId|a Vault AppRole Role ID with read/write access to cluster data| | |vaultSecretId|a Vault AppRole Secret ID with read/write access to cluster data| | |vaultToken|if not using AppRole, a Vault token can be used directly| | |vaultPrefix|prefix to the Vault data path|'kv/'|

Backend

Vault

Vault will have:

  • a map of Google service account keys at /credentials/google/${serviceAccountEmail}
  • a map of AWS IAM keys at /credentials/amazon/${accountName}
  • common provider specific data shared amongst clusters at /clusters/common/${provider}
  • a /clusters/all record whose value is a map of all clusterSlugs to their path in Vault, eg mycluster: '/clusters/production/mycluster'
  • a map of clusters /clusters/${environment}/${clusterSlug} containing all information specific to a single cluster. The record will have
    • A value key with a JSON blob of general cluster info, as defined by the schema.
    • A channels key with a JSON array of all channels the cluster belongs to
  • a /channels/all record whose value is a JSON array of all channels
  • a series of /channels/${channel} records whose value is a JSON array of clusterSlugs, that enumerates all clusters within a given channel

API

All client methods are async and return Promises.

getCluster(slug)

Gets all information about a single cluster.

const cluster = await client.getCluster('some-cluster')

assert.eql(cluster, {
    name: 'some-cluster',
    environment: 'production',
    props: {
        password: 'hunter2'
    },
    channels: ['production', 'p100']
})

listClusters()

Lists the names of all registered clusters.

const clusters = await client.listClusters()

assert.eql(clusters, [
    'some-cluster',
    'another-cluster'
])

registerCluster(slug, environment, props, [channels])

Registers a single cluster in the system. props go in vault. You can also optionally list the channels the cluster should be in. An error will be thrown if any of the channels do not exist.

await client.addCluster('some-cluster', 'staging', {password: 'hunter2'}, ['production'])

updateCluster(slug, newEnvironment, newProps)

Modify an existing cluster, replacing the existing environment and/or props with new sets. It is best to getCluster beforehand.

await client.updateCluster('some-cluster', 'dev', {password: 'hunter3'})

unregisterCluster(slug)

Un-register a cluster with the system. Channel associations will also be removed.

await client.removeCluster('some-cluster')

listChannels()

List all the registered channels.

const channels = await client.listChannels()
assert.eql(channels, [
    'production',
    'staging',
    'p100',
    'p200',
    'p300'
])

createChannel(channel)

Create a channel, so clusters can be added to it.

await client.createChannel('integration')

removeChannel(channel)

Removes a channel. Channel must have no clusters associated with it, otherwise an error is thrown.

await client.removeChannel('integration')

addClusterToChannel(slug, channel)

Adds a cluster to a channel. The cluster and channel must exist, otherwise an error is thrown.

await client.addClusterToChannel('some-cluster', 'production')

removeClusterFromChannel(slug, channel)

Removes a cluster to from a channel.

await client.removeClusterFromChannel('some-cluster', 'integration')

listClustersByChannel(channel)

Lists the names of all clusters within the specified cluster.

const clusters = await listClustersByChannel('production')

assert.eql(clusters, [
    'some-cluster',
    'another-cluster'
])

addServiceAccount(jsonServiceAccountKey)

Store a Service Account private key. Must be in JSON format.

const key = {
  'type': 'service_account',
  'project_id': 'my-project',
  'private_key_id': 'cccaedf234c3a4de25fce3adf245cfae352d4',
  'private_key': '-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n',
  'client_email': '[email protected]',
  'client_id': '22349780582375098234759',
  'auth_uri': 'https://accounts.google.com/o/oauth2/auth',
  'token_uri': 'https://oauth2.googleapis.com/token',
  'auth_provider_x509_cert_url': 'https://www.googleapis.com/oauth2/v1/certs',
  'client_x509_cert_url': 'https://www.googleapis.com/robot/v1/metadata/x509/my-sa1%40my-project.iam.gserviceaccount.com'
}
await addServiceAccount(key)

getServiceAccount(serviceAccountAddress)

Fetch a Service Account private key, given a client_email

const key = await getServiceAccount('[email protected]')

removeServiceAccount(serviceAccountAddress)

Delete a Service Account private key, given a client_email

await removeServiceAccount('[email protected]')

listServiceAccounts()

List the addresses of all stored Service Account keys.

const list = await listServiceAccounts()

assert.eql(list, [
    '[email protected]',
    '[email protected]',
    ...
])

getCommon(provider)

Get common defaults/values for all clusters for a given provider. (Default: 'GKE')

const data = await getCommon(provider)

assert.eql(data, {
  authAccount: '[email protected]',
  billingAccount: 123412341234,
  organizationId: 678967896789,
  clusterDefaults: {
    //...
  }
  //...
})

issueCertificate(role, domain, ttl = 5 * 60)

Issue a child certificate using Vault's PKI engine.

const resp = await issueCertificate('support-hub', 'my-cluster.npme.io')

assert.eql(resp, {
  certificate: '---- {PEM string}...',
  expiration: 1559166104,
  issuing_ca: '---- {PEM string}...',
  private_key: '---- {key string}...',
  private_key_type: 'rsa',
  serial_number: '52:be:c0:65:33:fa:6e:aa:02:60:10:be:c5:f7:f6:f4:a1:2c:3c:dc'
})

close()

Closes the client and any associated connections to backends.