Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 1,000,000+ packages pre-installed, including @fbl-plugins/k8s-helm with all npm packages installed. Try it out:

require("fbl/package.json"); // fbl is a peer dependency. var k8sHelm = require("@fbl-plugins/k8s-helm")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

@fbl-plugins/k8s-helm v1.2.0

FBL plugin for K8s Helm CLI

FBL Plugins: K8s Helm

Install, Update, Delete helm chart releases with ease in your fbl flows.

CircleCI Known Vulnerabilities codecov Total alerts Language grade: JavaScript

Purpose

fbl is a flow automation tool. That generally means it can automate any kind of routine processes and allows to create some really complex combinations of actions, even non related to deployment (probably, the main reason why you're currently reading this now).

While cluster deployment is in some cases really simple and some PaaS providers already support cluster creation withing few commands / mouse clicks, service deployment into the cluster is not trivial like that.

At FireBlink we generally treat entire cluster as a single product. As any other software product update of any of its dependencies may lead to unexpected behaviour. We never trust 3rd party vendors to have backward compatibility. So the only way we can be sure that all the services will work consistantly across environment is lock of the versions.

As cluster is a product, it has it's own version, migration scripts, and set of helm/kubectl commands required to stand up / update the cluster.

To help with that 2 main plugins for FBL has been created:

Generally both plugins are used together, as Secrets should be created outside the helm chart.

Sensitive information can be hosted inside the Git repo and encrypted with @fbl-plugins/crypto.

Flexibility of the deployment is the key concept of FBL and plugins, as we never know what challenges we need to resolve the following day.

Examples

Check fbl-examples repository for usage examples.

Integration

There are multiple ways how plugin can be integrated into your flow.

package.json

This is the most recommended way. Create package.json next to your flow file with following content:

{
  "name": "flow-name",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "fbl": "fbl"
  },
  "license": "UNLICENSED",
  "dependencies": {
    "@fbl-plugins/k8s-helm": "1.1.1",
    "fbl": "1.12.0"
  }
}

Then you can install dependencies as any other node module yarn install depending on the package manager of your choice.

After that you can use yarn fbl <args> to execute your flow or even register a custom script inside "scripts".

Global installation

npm i -g @fbl-plugins/k8s-helm

Register plugin to be accessible by fbl

  • via cli: fbl -p @fbl-plugins/k8s-helm <args>
  • via flow:
requires:
  fbl: '>=1.12.0 <2.0.0'
  plugins:
    '@fbl-plugins/k8s-helm': '>=1.1.1'

pipeline:
  # your flow goes here

Action Handlers

Metadata

RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free