heluxup
By using the flux helm operator it is possible to manage
helm charts in a git repository and flux takes care of the deployment.
heluxup is able to parse the flux control repository for HelmReleases and checks if updates of the charts are
available. If updates are available heluxup updates the yaml files in the flux control respositroy accordingly.
(It is possible to pass --dry-run to check the changes without modifying any files.)
Installation
Simply install heluxup with pip
$ pip install heluxup
or clone the repository
$ git clone git@github.com:ekeih/heluxup.git
$ cd heluxup
$ pip install -e .
Usage
$ heluxup /home/max/repos/flux-control/
Downloading all chart repository files can take a moment, please be patient.
Updating release ingress-controller (nginx-ingress) from 1.17.1 to 1.21.0
Updating release oauth2 (oauth2-proxy) from 0.14.0 to 0.14.1
Updating release cert-manager (cert-manager) from v0.9.1 to v0.10.0
Updating release omnbot-influxdb (influxdb) from 1.3.2 to 1.4.0
Updating release omnbot-redis (redis) from 9.1.2 to 9.1.12
Updating release prom (prometheus-operator) from 6.7.3 to 6.11.0
Updating release blackbox-exporter (prometheus-blackbox-exporter) from 1.1.0 to 1.3.0
Updating release kubewatch (kubewatch) from 0.8.5 to 0.8.9
Updating release loki (loki-stack) from 0.16.0 to 0.16.2
Updating release postgresql-production (postgresql) from 6.3.2 to 6.3.9
Updating release postgresql-development (postgresql) from 6.3.2 to 6.3.9
11 charts have been updated. Please verfiy the changes by running 'git diff' and make sure to read upstream docs for major updates.
If you are sure about the changes commit them to your flux repository to apply them to your cluster.
It is also possible to execute a dry-run which shows available updates without any modifications to the control repository.
$ heluxup -d /home/max/repos/flux-control/
[dry-run] Downloading all chart repository files can take a moment, please be patient.
[dry-run] Updating release ingress-controller (nginx-ingress) from 1.17.1 to 1.21.0
[dry-run] Updating release oauth2 (oauth2-proxy) from 0.14.0 to 0.14.1
[dry-run] Updating release cert-manager (cert-manager) from v0.9.1 to v0.10.0
[dry-run] Updating release omnbot-influxdb (influxdb) from 1.3.2 to 1.4.0
[dry-run] Updating release omnbot-redis (redis) from 9.1.2 to 9.1.12
[dry-run] Updating release prom (prometheus-operator) from 6.7.3 to 6.11.0
[dry-run] Updating release blackbox-exporter (prometheus-blackbox-exporter) from 1.1.0 to 1.3.0
[dry-run] Updating release kubewatch (kubewatch) from 0.8.5 to 0.8.9
[dry-run] Updating release loki (loki-stack) from 0.16.0 to 0.16.2
[dry-run] Updating release postgresql-production (postgresql) from 6.3.2 to 6.3.9
[dry-run] Updating release postgresql-development (postgresql) from 6.3.2 to 6.3.9
[dry-run] 11 charts have been updated. Please verfiy the changes by running 'git diff' and make sure to read upstream docs for major updates.
[dry-run] If you are sure about the changes commit them to your flux repository to apply them to your cluster.
Release
- Tag a new release
git tag 0.2.0 - Push it
git push origin 0.2.0 - The CI will build a new package and release it to PyPI
- To build a new AUR package clone
ssh://aur@aur.archlinux.org/heluxup.git - Adjust the version and dependencies in PKGBUILD
- Run
makepkg --printsrcinfo > .SRCINFO - Commit the changes and push the AUR package
License
heluxup makes it easy to upgrade HelmRelease objects in a flux control respository.
Copyright (C) 2019 Max Rosin
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Metadata
Release files for heluxup 1.0.2
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 | Actions |
|---|---|---|---|---|
| heluxup-1.0.2.tar.gz | 4.4 kB | Without provenance | Details for heluxup-1.0.2.tar.gz |
Release files / heluxup-1.0.2.tar.gz
| Download URL | heluxup-1.0.2.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21a14b5b499ef5865f08ca5c97770ab12a5f15cd8d238374ec7967ee815ba63e
|
|
BLAKE2b-256 checksum How to use checksums |
c14cf702649f93c1a415043329c66505ba7f0f4a42bf11f9a3769b9faf01d9af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.39.0 CPython/3.7.5
|
Security for heluxup 1.0.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.