# CNR Command Line Tool
## Install the Helm Registry Plugin
First, Install the latest [Helm release](https://github.com/kubernetes/helm#install).
If you are an OSX user, quickstart with brew: brew install kubernetes-helm
Next download and install the registry plugin for Helm.
### OSX
` wget https://github.com/cn-app-registry/cnr-cli/releases/download/v0.3.7-dev/registry-cnr-v0.3.7-dev-osx-x64-helm-plugin.tar.gz mkdir -p ~/.helm/plugins/ tar xzvf registry-cnr-v0.3.7-dev-osx-x64-helm-plugin.tar.gz -C ~/.helm/plugins/ `
### Linux
` wget https://github.com/cn-app-registry/cnr-cli/releases/download/v0.3.7-dev/registry-cnr-v0.3.7-dev-linux-x64-helm-plugin.tar.gz mkdir -p ~/.helm/plugins/ tar xzvf registry-cnr-v0.3.7-dev-linux-x64-helm-plugin.tar.gz -C ~/.helm/plugins/ `
### Windows
` wget https://github.com/cn-app-registry/cnr-cli/releases/download/v0.3.7-dev/registry-cnr-v0.3.7-dev-win-x64-helm-plugin.tar.gz mkdir -p ~/.helm/plugins/ tar xzvf registry-cnr-v0.3.7-dev-linux-x64-helm-plugin.tar.gz -C ~/.helm/plugins/ `
Note: You must have bash in your path and change the registry/plugin.yaml execution to call bash -c $HELM_PLUGIN_DIR/cnr.sh
## Deploy Jenkins Using Helm from the Quay Registry
` helm registry version app.quay.io `
Output should be: ` Api-version: {u'cnr-api': u'0.X.Y'} Client-version: 0.X.Y `
### Install Jenkins
` helm init helm registry list app.quay.io helm registry install app.quay.io/helm/jenkins `
## Create and Push Your Own Chart
First, create an account on https://app.quay.io (staging server) and login to the CLI using the username and password
Set an environment for the username created at Quay to use through the rest of these instructions.
` export USERNAME=philips `
Login to Quay with the Helm registry plugin:
` helm registry login -u $USERNAME app.quay.io `
Create a new Helm chart, the default will create a sample nginx application:
` helm create nginx `
Push this new chart to Quay and then deploy it from Quay.
` cd nginx helm registry push --namespace $USERNAME app.quay.io helm registry install app.quay.io/$USERNAME/nginx `
Metadata
Release files for cnr 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cnr-0.4.1.tar.gz | 21.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cnr-0.4.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 52.3 kB
Release files / cnr-0.4.1.tar.gz
| Download URL | cnr-0.4.1.tar.gz |
|---|---|
| Size | 21.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a59ac5d1a5605b8f663591806c0ea0cf571e13ad4186b5d4932a49bbdc2d784
|
|
BLAKE2b-256 checksum How to use checksums |
d99a178506158b3c1b0e2dbeea473853cc866d01892ca4d426a64c0dadd5e6ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / cnr-0.4.1-py2.py3-none-any.whl
| Download URL | cnr-0.4.1-py2.py3-none-any.whl |
|---|---|
| Size | 30.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4b1f8b25a5033bb981f59055b608bfefeb04e55e078506a5f569cb6216a9cce6
|
|
BLAKE2b-256 checksum How to use checksums |
066d9b38989470dc773130dc3b9a6231c8f670dfaffabe72cbe5826eeac09776
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cnr 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.