ChartPress: render and publish helm charts and images
Project description
chartpress
Chartpress automate basic Helm chart development work. It is tightly used in development of the JupyterHub and BinderHub Helm charts.
Features
Chartpress can do the following with the help of some configuration.
- Update Chart.yaml's version appropriately
- Build docker images and tag them appropriately
- Push built images to a docker iamge repository
- Update values.yaml to reference the built images
- Publish a chart to a Helm chart repository based on GitHub pages
- Reset changes to Chart.yaml and values.yaml
Requirements
The following binaries must be in your PATH
:
If you are publishing a chart to GitHub Pages create a gh-pages
branch in the
destination repository.
Installation
pip install chartpress
Usage
In a directory containing a chartpress.yaml
, run:
chartpress
to build your chart(s) and image(s). Add --push
to publish images to docker
hub and --publish-chart
to publish the chart and index to gh-pages.
usage: chartpress [-h] [--push] [--publish-chart]
[--extra-message EXTRA_MESSAGE] [--tag TAG | --long]
[--image-prefix IMAGE_PREFIX] [--reset] [--skip-build]
[--version] [--commit-range COMMIT_RANGE]
Automate building and publishing helm charts and associated images. This is
used as part of the JupyterHub and Binder projects.
optional arguments:
-h, --help show this help message and exit
--push Push built images to their docker image registry.
--publish-chart Package a Helm chart and publish it to a Helm chart
repository contructed with a GitHub git repository and
GitHub pages.
--extra-message EXTRA_MESSAGE
Extra message to add to the commit message when
publishing charts.
--tag TAG Explicitly set the image tags and chart version.
--long Use this to always get a build suffix for the
generated tag and chart version, even when the
specific commit has a tag.
--image-prefix IMAGE_PREFIX
Override the configured image prefix with this value.
--reset Skip image build step and reset Chart.yaml's version
field and values.yaml's image tags. What it resets to
can be configured in chartpress.yaml with the resetTag
and resetVersion configurations.
--skip-build Skip the image build step.
--version Print current chartpress version and exit.
--commit-range COMMIT_RANGE
Deprecated: this flag will be ignored. The new logic
to determine if an image needs to be rebuilt does not
require this. It will find the time in git history
where the image was last in need of a rebuild due to
changes, and check if that build exists locally or
remotely already.
Configuration
A chartpress.yaml
file contains a specification of charts and images to build
for each chart. Below is an example chartpress.yaml
file.
charts:
# list of charts by name
# each name should be a directory containing a helm chart
- name: binderhub
# the prefix to use for built images
imagePrefix: jupyterhub/k8s-
# tag to use when resetting the chart values
# with the --reset flag. It defaults to "set-by-chartpress".
resetTag: latest
# version to use when resetting the Chart.yaml's version field with the
# --reset flag. It defaults to "0.0.1-set.by.chartpress". This is a valid
# SemVer 2 version, which is required for a helm lint command to succeed.
resetVersion: 1.2.3
# the git repo whose gh-pages contains the charts
repo:
git: jupyterhub/helm-chart
published: https://jupyterhub.github.io/helm-chart
# additional paths (if any) relevant to the chart version
# outside the chart directory itself
paths:
- ../setup.py
- ../binderhub
# images to build for this chart (optional)
images:
binderhub:
# Template docker build arguments to be passed using docker's
# --build-arg flag as --build-arg <key>=<value>. Available dynamic
# values are TAG and LAST_COMMIT.
buildArgs:
MY_STATIC_BUILD_ARG: "hello world"
MY_DYNAMIC_BUILD_ARG: "{TAG}-{LAST_COMMIT}"
# Context to send to docker build for use by the Dockerfile
# (if different from the current directory)
contextPath: ..
# Dockerfile path, if different from the default
# (may be needed if contextPath is set)
dockerfilePath: images/binderhub/Dockerfile
# path(s) in values.yaml to be updated with image name and tag
valuesPath:
- singleuser.image
- singleuser.profileList.0.kubespawner_override.image
# additional paths (if any) relevant to the image
# outside the image directory itself
paths:
- ../setup.py
- ../binderhub
Caveats
TravisCI mirror image registry
If you run chartpress on TravisCI, its logic can be fooled by a mirror image registry to rebuild something that didn't need rebuilding. A workaround for this can be found in this repo's .travis.yml.
Shallow clones
Chartpress detects the latest commit which changed a directory or file when determining the version and tag to use for charts and images. This means that shallow clones should not be used because if the last commit that changed a relevant file is outside the shallow commit range, the wrong tag will be assigned.
TravisCI uses a clone depth of 50 by default, which can result in incorrect
image tagging. You can disable this shallow clone
behavior
in your .travis.yml
:
git:
depth: false
Development
Testing of this python package can be done using pyflakes
and pytest
. There is also some additional testing that is only run as part of TravisCI, as declared in .travis.yml
.
# install chartpress locally
pip install -e .
# install dev dependencies
pip install pyflakes pytest
# run tests
pyflakes .
pytest -v
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Hashes for chartpress-0.4.3-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | ba88f88339a3102cc4183a19d234e5377ef40ff19f15f9b449092244b40d86d1 |
|
MD5 | 584b6f4cc7ffc90603efe7c788932349 |
|
BLAKE2b-256 | 337e55760708f44db6298b3c39b0c1d253a839f7657aceb490a287b71c8a43b4 |