open-index/open-npm huggingface dataset:
npm package: @provisioner/istio
Description: CodeZero provisioner for Istio
Author: Grant Burnard
Latest version: 0.0.31

# Istio Provisioner


Current Hub manifest for web install must be set as follows:

```json
{
    "_id" : "01E12NGHHHRFZ7HPBSXE3FZ78F",
    "name" : "istio",
    "namespace" : "istio",
    "spec" : {
        "services" : [ 
            {
                "istio" : {
                    "ingressEnabled" : true,
                    "citadelEnabled" : false,
                    "telemetryEnabled" : false,
                    "grafanaEnabled" : false,
                    "kialiEnabled" : false,
                    "prometheusEnabled" : false,
                    "grafanaAdminUsername" : "admin",
                    "grafanaAdminPassword" : "admin"
                }
            }
        ]
    },
    "admin" : [ 
        "01DV7D6VPG0XYBX7S5AF8RXE53"
    ],
    "read" : [],
    "write" : [],
    "createdOn" : ISODate("2020-02-14T20:16:17.970Z")
}
```

# Generating the scripts

When upgrading to use a newer version of Istio, you will need to regenerate the istio provisioning scripts in order to ensure they're configured and separated properly for the istio provisioner, including the namespace tokens.

## Setup your istio path if it isn't already
Be sure to point to the correct Istio folder and version.  `export PATH=$PATH:.../istio-1.x.x/bin`

## Run the generation script
`cd build`
`./gen.sh`

## Check in the results
Review the .yaml files (inside of the k8s folder) and then commit the latest istio provisioning files.
npm package: @provisioner/logging-elk
Description: CodeZero provisioner for logging (ELK stack)
Author: Grant Burnard
Latest version: 0.0.31

# Logging Provisioner

This logging app installs Elasticsearch, Logstash, and Kibana (ELK stack) and with Fluentd in your cluster.

## Parameters

| Parameter | Meaning |
| --------- | ------- |
| storage | Persistent volume storage space (defaults to 1Gi)

## Notes

1. Elasticsearch listens at "elasticsearch.[namespace].svc.cluster.local:9200" (RESTful)
1. Kibana listens at "http://kibana.[namespace].svc.cluster.local:5601"

## Background

1. [How To Set Up an Elasticsearch, Fluentd and Kibana (EFK) Logging Stack on Kubernetes](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-elasticsearch-fluentd-and-kibana-efk-logging-stack-on-kubernetes)
1. [Configuring the elasticsearch output plugin](https://docs.fluentd.org/output/elasticsearch#hosts-(optional))
npm package: @provisioner/node-red
Description: CodeZero provisioner for node-red
Author: Mike Blackstock
Latest version: 0.0.17

# Node-RED Provisioner

## Build

At the root of the c6o node-monorepo:

```bash
yarn build --scope=@provisioner/node-red
```

## Run from CLI

To run the provisioner, create a `traxitt.yaml` file, for example:

```yaml
name: node-red
version: 0.0.1
description: Node-RED provisioner
services:
  - node-red:
      storage: 2Gi      # default 1Gi
      projects: false   # default false
```

Drop it into a directory like `~/provisioners/node-red/traxitt.yaml`, then execute

```bash
czctl provision ~/provisioners/node-red
```

To test out Node-RED once it's running in a cluster:

``` bash
kubectl -n node-red-ns port-forward services/node-red 1880:1880
```

Then point your browser to `http://localhost:1880`

## Parameters

| Parameter | Meaning |
| --------- | ------- |
| storage | PVC storage for flows, and related storage needed by nodes.
| projects | when true, enables the Node-RED projects feature.  This use for flow development, not running flows |

## Server paths

The provisioner module `serve` method handles HTTP requets for an express server.  The serve function supports the following paths:

| Path | Contents |
| --------- | ------- |
| index.js | implementation of `<nodered-capacity>` for use in the configuration wizard |
npm package: @provisioner/vscode
Description: CodeZero provisioner for vscode
Author: Narayan Sainaney
Latest version: 0.0.31

# VS Code Provisioner

## Build
At the root of the c6o node-monorepo:

```bash
yarn build --scope=@provisioner/vscode
```

## Run from CLI

To run the provisioner, create a `traxitt.yaml` file, for example:

```yaml
name: vscode
namespace: vscode
version: 0.0.1
description: This is the installer spec for the vscode remote development environment
services:
    - vscode:
        launch: true                # default false/undefined
        storage: 4Gi                # default 4Gi
        publicKey: "public rsa key" # default undefined
```

Drop it into a directory like `~/provisioners/vscode`, then execute

```bash
czctl provision ~/provisioners/vscode
```

To test out VSCode once it's installed in a cluster:

``` bash
code --folder-uri vscode-remote://ssh-remote%2Broot@${externalIP}/data
```

Where the IP address is the IP address of the provisioned LoadBalancer external IP.  To get this (for example):

```
kubectl get svc -n vscode

NAME              TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)          AGE
dev-pod-ssh-svc   LoadBalancer   10.245.81.114   138.197.236.7   22:30579/TCP     2m56s
dev-pod-svc       NodePort       10.245.66.7     <none>          3030:30361/TCP   2m55s
```

## Parameters

| Parameter | Meaning |
| --------- | ------- |
| launch | true to launch VSCode from c6o CLI |
| storage | PVC storage for development |
| publicKey | contents of ssh public key used for authentication.  If not defined, provisioner copies `id_rsa.pub` from `~/.ssh` |

## Server paths

The provisioner module `serve` method handles HTTP requets for an express server.  The serve function supports the following paths:

| Path | Contents |
| --------- | ------- |
| index.js | implementation of `<vscode-capacity>` for use in the configuration wizard |