gsaslis/operator-csv-semver-bump repository overview

⁠SemVer Bumps for Kubernetes Operator CSVs

A container image that handles bumping Kubernetes Operator Metadata ClusterServiceVersion yaml files.

We all know the value of Semantic Versioning⁠. Yet, the actual version bumping, is tedious and error prone. Not to mention that I'm sure you have better ways of spending your time⁠.

This container image helps with taking care of the version bumping of CSVs.

⁠Usage

⁠Requirements

• An Operator Lifecycle Manager (OLM)-compatible operator
• Your operator manifests in some directory in your filesystem
• Each version of the manifests in a separate sub-folder, inside the manifests directory. The name of the sub-folder is expected to be the version name (e.g. 0.1.2, 0.3.5, 1.9.0, etc.)
• The channel name should end with -$major.$minor, e.g. threescale-0.2, threescale-2.8, threescale-3.0 and so on...
• The channel currentCSV should be of the format: $package_name.v$major.$minor.$patch

Here is an example of the folder structure, from the 3scale Apicast API Gateway Operator⁠:

$ tree .
.
├── Dockerfile
├── Makefile
├── container.yaml
└── manifests
    ├── apicast-operator.v0.3.0.clusterserviceversion.yaml
    └── apps_v1alpha1_apicast_crd.yaml
└── metadata
    └── annotations.yaml

⁠Bump Version

To actually bump the version and create the folders and files, run the container, replacing the below PATH_TO_MANIFESTS with the appropriate path on your filesystem.

 docker run -v <PATH_TO_METADATA_REPO>:/workdir gsaslis/operator-csv-semver-bump minor

⁠Acknowledgements

The bumping logic is appropriated from @jonastl's⁠ project bump-semver⁠ .