stackabletech / stackabletech/docker-images

chore(hbase-phoenix-omid): Update major/minor versions for 26.11.0

Open
#1,647 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

scheduled-for/26.11.0
Dominant language
Dockerfile
Stars
22
Forks
6
Avg merge
16h 59m
Merged PRs (30d)
30

Description

Part of https://github.com/stackabletech/docker-images/issues/1641.

HBase

  • Add: 3.0.0 (experimental) (Experimental status TBD)
  • Remove: 2.6.4

Phoenix

  • Add: 5.3.2 (supported)
  • Deprecate: 5.3.1
  • Remove: 5.3.0

[!TIP]
Please add to the Stackable Engineering project.

Update tasks

HBase and Phoenix
  • Update boil-config.toml to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
  • Upload new versions (see the hbase/*.sh scripts).
  • Update boil-config.toml to the latest supported version of JVM (base and devel).
  • Update boil-config.toml to the latest supported version of Hadoop.
  • Update boil-config.toml of spark-k8s/hbase-connectors to the latest supported version of HBase, hbase-thridparty and protobuf.
  • Update other dependencies if applicable (eg: phoenix, opa_authorizer, etc).
  • Check other operators (getting_started / kuttl / supported-versions) for usage of the versions. Add the PR to the list below.
Omid

None.

Related Pull Requests

[!TIP]
Delete any items that do not apply so that all applicable items can be checked.
For example, if you add release notes to the documentation repository, you do not need the latter two criteria.

  • Link to the docker-images PR (product update)
  • Link to operator PR (getting_started / kuttl)
  • Link to any other operator PRs (getting_started / kuttl)
  • Link to demo PR (raise against the main branch)
  • Link to the Release Notes PR in the documentation repo (if not a comment below)

Acceptance

[!TIP]
This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been
checked, the issue can be moved into Development: Done.

  • Can build image (either locally, or in CI)
  • All kuttl tests pass (either locally, or in CI)
  • Release notes added to documentation and linked as a PR above
  • Release notes written in a comment below
  • Applicable release-note label added to this issue
Testing instructions
# Where x.y.z is the new version added in this PR
boil build hbase=x.y.z --strip-architecture --load
boil build omid=x.y.z --strip-architecture --load

kind load docker-image oci.stackable.tech/sdp/hbase:x.y.z-stackable0.0.0-dev
kind load docker-image oci.stackable.tech/sdp/omid:x.y.z-stackable0.0.0-dev

# Change directory into the hbase-operator repository and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar
./scripts/run-tests --test omid

Please consider updating this template if these instructions are wrong, or
could be made clearer.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the HBase and Phoenix entries in boil-config.toml and the hbase/*.sh upload scripts, using the agreed versions in the spreadsheet as the source of truth. Check the referenced spark-k8s/hbase-connectors and operator getting_started, kuttl, and supported-versions files for dependent versions. Run the listed boil build commands and operator test commands; done means images build, applicable tests pass, release notes are linked, and acceptance items are checked.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, dockerfile, kubernetes, shell
Domain
build-system, databases, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.