Part of #722.
This is for tracking distributed work. For instructions on how to proceed with each operator, see the description below.
Please follow this list in order at least until the zookeeper-operator before parallelizing.
Description
This is a list of steps you can follow to generate, install and test Operator Lifecycle Management (OLM) manifests for the Stackable Data Platform.
The manigest generation is fully automated for all operators except two: the secret and the listener operator. These two required manual intervention.
OLM manifests can be generated at any time and for any version of the operators (including 0.0.0-dev) but it's specially needed after a platform release, to certify the new operator versions.
To generate manifests for a released version of the SDP, ensure that you checkout the appropriate branch of the operator repository and the openshift operator repository.
Pre-requisites
In addition to the usual development tools like git and Python you need to clone the following repositories, idealy in the same location (this guide assumes $HOME/repo/stackable):
This issue assumes you are generating OLM manifests for a released SDP version with the intention of certifying it. This means:
Secret and listener operator
Generate manifests
Options:
-r 25.7.0 is the SDP release
-c $HOME/repo/stackable/openshift-certified-operators the location of the openshift operator repository
-o $HOME/repo/stackable/secret-operator the location of the secret op
Install manifests
Options:
-r 25.7.0 version of the operator to install
-o secret name of the operator to install
-c ~/repo/stackable/openshift-certified-operators location of the openshift operator repository
-d deploy to the cluster
All other operators
These operators shouldn't require any manual editing of the manifests but a visual check is recommended.
The steps are illustrated only once for the ZooKeeper operator but a list of all operators to work on is added below.
Generate manifests
See ./olm/build-manifests.py --help for possible options.
Install manifests
./olm/build-bundles.sh \
-r 25.7.0 \
-o zookeeper \
-c ~/repo/stackable/openshift-certified-operators \
-d
Test the operator
Run the openshit integration test suite for the operator
cd ~/repo/stackable/zookeeper-operator
/scripts/run-tests --test-suite openshift --skip-operator zookeeper
We use --skip-operator because the operator has already been installed previously.
Part of #722.
This is for tracking distributed work. For instructions on how to proceed with each operator, see the description below.
Please follow this list in order at least until the zookeeper-operator before parallelizing.
Description
This is a list of steps you can follow to generate, install and test Operator Lifecycle Management (OLM) manifests for the Stackable Data Platform.
The manigest generation is fully automated for all operators except two: the
secretand thelisteneroperator. These two required manual intervention.OLM manifests can be generated at any time and for any version of the operators (including
0.0.0-dev) but it's specially needed after a platform release, to certify the new operator versions.To generate manifests for a released version of the SDP, ensure that you checkout the appropriate branch of the operator repository and the openshift operator repository.
Pre-requisites
In addition to the usual development tools like
gitandPythonyou need to clone the following repositories, idealy in the same location (this guide assumes$HOME/repo/stackable):This issue assumes you are generating OLM manifests for a released SDP version with the intention of certifying it. This means:
Secret and listener operator
Generate manifests
Update the supported OpenShift version range in the function generate_metadata()
Create release branch (from
main) in the openshift operator repositoryGenerate manifests
Options:
-r 25.7.0is the SDP release-c $HOME/repo/stackable/openshift-certified-operatorsthe location of the openshift operator repository-o $HOME/repo/stackable/secret-operatorthe location of the secret optemplate.specandrulesfrom the newly generated files.Install manifests
Ensure your K8S configuration points to a an OpenShift (or OKD) instance
Install the operator from the manifests generated in the previous step
/olm/build-bundles.sh -r 25.7.0 -o secret -c ~/repo/stackable/openshift-certified-operators -dOptions:
-r 25.7.0version of the operator to install-o secretname of the operator to install-c ~/repo/stackable/openshift-certified-operatorslocation of the openshift operator repository-ddeploy to the clusterAll other operators
These operators shouldn't require any manual editing of the manifests but a visual check is recommended.
The steps are illustrated only once for the ZooKeeper operator but a list of all operators to work on is added below.
Generate manifests
Create release branch (from
main) in the openshift operator repositoryEnsure appropriate branch (
release-25.7) is checkout out in the ZooKeeper operatorGenerate manifests
See
./olm/build-manifests.py --helpfor possible options.Install manifests
./olm/build-bundles.sh \ -r 25.7.0 \ -o zookeeper \ -c ~/repo/stackable/openshift-certified-operators \ -dTest the operator
Run the openshit integration test suite for the operator
We use
--skip-operatorbecause the operator has already been installed previously.