Skip to content

OLM Manifests for SDP Release 25.3 #714

@razvan

Description

@razvan

Tracking

Part of #686

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 for the first five operators (up to the opa operator).


Operator Maintainer Branch Kuttl Tests Cert PR Notes
commons @razvan stackable-commons-25.3.0 redhat-openshift-ecosystem/certified-operators#5552 Related PR stackabletech/stackable-utils#102
secret @razvan stackable-secret-25.3.0 redhat-openshift-ecosystem/certified-operators#5553
listener @razvan stackable-listener-25.3.0 redhat-openshift-ecosystem/certified-operators#5554
zookeeper @razvan stackable-zookeeper-25.3.0 redhat-openshift-ecosystem/certified-operators#5555
opa @razvan stackable-opa-25.3.0 redhat-openshift-ecosystem/certified-operators#5556
hdfs @razvan stackable-hdfs-25.3.0 redhat-openshift-ecosystem/certified-operators#5557
hive @razvan stackable-hive-25.3.0 redhat-openshift-ecosystem/certified-operators#5558
hbase @razvan stackable-hbase-25.3.0 redhat-openshift-ecosystem/certified-operators#5559
druid @razvan stackable-druid-25.3.0 redhat-openshift-ecosystem/certified-operators#5560
kafka @razvan stackable-kafka-25.3.0 redhat-openshift-ecosystem/certified-operators#5561
nifi @razvan stackable-nifi-25.3.0 redhat-openshift-ecosystem/certified-operators#5563
spark @razvan stackable-spark-25.3.0 redhat-openshift-ecosystem/certified-operators#5564
superset @razvan stackable-superset-25.3.0 redhat-openshift-ecosystem/certified-operators#5565
airflow @razvan stackable-airflow-25.3.0 redhat-openshift-ecosystem/certified-operators#5566
trino @razvan stackable-trino-25.3.0 redhat-openshift-ecosystem/certified-operators#5567

Description

This is a list of steps you can follow to generate, install and test Operator Life-cycle Management (OLM) manifests for the Stackable Data Platform.

The manifest 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:

  • All operator repositories have the required release branch. These releases have been tested and are generally available.
  • All container images have been published to quay.io

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 repository

    cd $HOME/repo/stackable/openshift-certified-operators
    git switch -c stackable-secret-25.3.0
    
  • Generate manifests

    ./olm/build-manifests.sh -r 25.3.0 \
    -c $HOME/repo/stackable/openshift-certified-operators \
    -o $HOME/repo/stackable/secret-operator
    

Options:

  • -r 25.3.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
  • Copy the cluster service version file from the previous version.
  • Copy the operator manifests file fro the previous version. For secret and listener
  • Replace the contents of the deployment, and cluster role with the template.spec and rules from the newly generated files.
  • Remove the unused generated files : service account, operator cluster role (not the product cluster role), role binding, deployment.
  • Remove all Helm labels in all remaining files (including all labels from the cluster role).
  • Check or update the metadata/dependencies.yaml
  • Update image tags and hashes with quay.io versions
  • Commit & push your changes

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.3.0 -o secret -c ~/repo/stackable/openshift-certified-operators -d
    

Options:

  • -r 25.3.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

  • Create release branch (from main) in the openshift operator repository

    cd $HOME/repo/stackable/openshift-certified-operators
    git switch -c stackable-zookeeper-25.3.0
    
  • Ensure appropriate branch (release-25.3) is checkout out in the ZooKeeper operator

  • Generate manifests

    ./olm/build-manifests.py  \
    --openshift-versions v4.14-v4.17 \
    --repo-certified-operators ~/repo/stackable/openshift-certified-operators \
    --channel 25.3 \
    --release 25.3.0 \
    --repo-operator ~/repo/stackable/zookeeper-operator
    

See ./olm/build-manifests.py --help for possible options.

Important

The --replaces argument was not used because the previous release 24.11.1 was not certified for 4.17.

Install manifests

./olm/build-bundles.sh \
-r 25.3.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.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions