Release Notes - v1.0.7¶

Release Date: March 19, 2026
Status: Ready for Submission to Community Operators

Overview¶

Version 1.0.7 extends OpenShift support to include versions 4.21 and 4.22, bringing the total supported range to OpenShift 4.18 - 4.22. This release includes all critical fixes from the catalog visibility investigation and has been validated on OKD 4.22.

What's New¶

Extended OpenShift Support¶

OpenShift Version Range: v4.18-v4.22 (previously v4.18-v4.20)
Kubernetes Support: 1.28+ (tested up to 1.35.1)
Added com.redhat.openshift.versions annotation to CSV for proper catalog filtering

OpenShift/Kubernetes Version Mapping¶

OpenShift	Kubernetes	Status
4.18	1.31	Maintenance (EUS)
4.19	1.32	Full Support
4.20	1.33	Full Support (EUS)
4.21	1.34	Expected Feb 2026
4.22	1.35	Expected ~Jun 2026 (EUS)

Bug Fixes¶

Critical Fixes Included¶

kube-rbac-proxy Image Fix
Changed from deprecated gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0
To working quay.io/brancz/kube-rbac-proxy:v0.18.0
Fixes ImagePullBackOff errors preventing metrics proxy from starting
Channel Mismatch Fix
Updated bundle metadata from alpha to stable channel
Ensures consistency with catalog definition

Technical Details¶

Bundle Information¶

Version: 1.0.7
Replaces: jupyter-notebook-validator-operator.v1.0.6
Channel: stable
minKubeVersion: 1.28.0

Container Images¶

Operator: quay.io/takinosh/jupyter-notebook-validator-operator:1.0.7
Bundle: quay.io/takinosh/jupyter-notebook-validator-operator-bundle:1.0.7

Validation Status¶

✅ Bundle validated with operator-sdk v1.37.0
✅ Basic validation passed
✅ Operator Framework validation suite passed
✅ Tested on OKD 4.22.0-okd-scos.ec.9 (Kubernetes v1.35.1)
✅ Test notebook validation succeeded

Compatibility¶

Supported Platforms¶

Kubernetes: 1.28+
OpenShift: 4.18 - 4.22
OKD: 4.18 - 4.22
Tekton Pipelines: v0.68+ (OpenShift Pipelines 1.20+)

API Compatibility¶

Uses k8s.io v0.31.x (Kubernetes 1.31 APIs)
Compatible with Kubernetes 1.28 - 1.35+
No deprecated APIs used
Forward compatible with future Kubernetes versions

Upgrade Path¶

From v1.0.6¶

spec:
  replaces: jupyter-notebook-validator-operator.v1.0.6

The operator will automatically upgrade from v1.0.6 to v1.0.7 when available in the catalog.

Upgrade Chain¶

v1.0.5 → v1.0.6 → v1.0.7

Installation¶

Prerequisites¶

OpenShift 4.18+ or OKD 4.18+ or Kubernetes 1.28+
Operator Lifecycle Manager (OLM) installed
cert-manager (for webhooks)

Via OperatorHub (After PR Merge)¶

Navigate to OperatorHub in OpenShift/OKD Console
Search for "Jupyter Notebook Validator Operator"
Click Install
Select "stable" channel
Choose installation mode and namespace

Via CLI¶

# Create namespace
oc create namespace jupyter-notebook-validator-operator

# Create OperatorGroup
cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: jupyter-notebook-validator-operator-group
  namespace: jupyter-notebook-validator-operator
spec:
  targetNamespaces:
  - jupyter-notebook-validator-operator
EOF

# Create Subscription
cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: jupyter-notebook-validator-operator
  namespace: jupyter-notebook-validator-operator
spec:
  channel: stable
  name: jupyter-notebook-validator-operator
  source: community-operators
  sourceNamespace: openshift-marketplace
  installPlanApproval: Automatic
  startingCSV: jupyter-notebook-validator-operator.v1.0.7
EOF

Testing¶

Validation Status¶

Bundle Validation:

✅ Bundle structure validation: PASSED
✅ operator-sdk bundle validate: PASSED
✅ Operator Framework suite: PASSED

Manual Testing on OKD 4.22:

✅ Deployment on OKD 4.22: PASSED
✅ Test notebook execution: PASSED
✅ Webhooks operational: PASSED
✅ Metrics proxy running: PASSED

CI Pipeline Status:

✅ OLM Bundle Validation: PASSED
✅ E2E - Kind Cluster Tests (Tier 1): PASSED
✅ Build and Push Image: PASSED
❌ Unit Tests: FAILING (BeforeSuite setup issue)
❌ CI - Unit & Integration Tests: FAILING (dependent on unit tests)
❌ E2E - OpenShift Cluster Tests: SKIPPED (requires live cluster)

Test Environment¶

Manual Testing Cluster: OKD 4.22.0-okd-scos.ec.9
Kubernetes: v1.35.1
Architecture: Single Node OpenShift (SNO)
Test Notebook: notebooks/tier1-simple/01-hello-world.ipynb
Test Repository: https://github.com/tosin2013/jupyter-notebook-validator-test-notebooks

Known Issues¶

Unit tests failing in CI: BeforeSuite setup issue in controller tests (needs investigation)
Not tested on all OpenShift versions: Only manually validated on OKD 4.22
OpenShift 4.18-4.21 compatibility: Assumed based on API compatibility, not explicitly tested

Submission Status¶

Next Steps¶

Build and Push Images

make docker-build docker-push IMG=quay.io/takinosh/jupyter-notebook-validator-operator:1.0.7
make bundle-build bundle-push BUNDLE_IMG=quay.io/takinosh/jupyter-notebook-validator-operator-bundle:1.0.7

Submit to community-operators-prod
Repository: redhat-openshift-ecosystem/community-operators-prod
Target: OpenShift/OKD OperatorHub
PR Title: "operator jupyter-notebook-validator-operator (1.0.7)"
Update k8s-operatorhub/community-operators (if needed)
Repository: k8s-operatorhub/community-operators
Target: OperatorHub.io (Kubernetes)
Note: PR #7235 already has v1.0.7-1.0.9, verify kube-rbac-proxy fix

Known Issues¶

None at this time.

Breaking Changes¶

None. This is a backward-compatible release.

Deprecations¶

None.

Contributors¶

Tosin Akinosho (@tosin2013)

References¶

GitHub Repository: https://github.com/tosin2013/jupyter-notebook-validator-operator
Documentation: https://github.com/tosin2013/jupyter-notebook-validator-operator/tree/main/docs
Issue Tracker: https://github.com/tosin2013/jupyter-notebook-validator-operator/issues
Investigation Report: docs/CATALOG-VISIBILITY-INVESTIGATION.md
OpenShift Support Matrix: docs/OPENSHIFT_SUPPORT_MATRIX_AND_STRATEGY.md

Support¶

Maintainer: Tosin Akinosho takinosh@redhat.com
Provider: Decision Crafters
Community: GitHub Issues and Discussions

Note: This release is ready for submission to community-operators repositories. Images need to be built and pushed before creating the PR.