operators jupyter-notebook-validator-operator (1.0.2, 1.0.3-ocp4.19, …

[tosin2013]

…1.0.4, 1.0.5)

Initial submission of Jupyter Notebook Validator Operator to community-operators-prod.

Versions included:

• 1.0.2: Initial release for OpenShift 4.18
• 1.0.3-ocp4.19: OpenShift 4.19 specific release
• 1.0.4: Multi-OpenShift support (4.18, 4.19, 4.20)
• 1.0.5: Universal release for all OpenShift versions

Features:

• Validate Jupyter notebooks in Kubernetes/OpenShift
• Git-based notebook fetching
• S2I build integration
• Model validation support
• Prometheus metrics
• Admission webhooks

Container Images (all publicly accessible on quay.io):

• quay.io/takinosh/jupyter-notebook-validator-operator:1.0.2-ocp4.18
• quay.io/takinosh/jupyter-notebook-validator-operator:1.0.3-ocp4.19
• quay.io/takinosh/jupyter-notebook-validator-operator:1.0.4
• quay.io/takinosh/jupyter-notebook-validator-operator:1.0.5

Tested on Kubernetes v1.29.0, v1.30.0, v1.31.0, v1.33.0 with OLM v0.28.0

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.

New Submissions

• Are you familiar with our contribution guidelines?
• Are you familiar with our operator pipeline?
• Have you tested your Operator with all Custom Resource Definitions packaging?
• Have you tested your Operator in all supported installation modes?
• Have you considered whether you want to use semantic versioning order?
• Is your submission signed?
• Is operator icon set?

Your submission should not

• Add more than one operator bundle per PR
• Modify any operator
• Rename an operator
• Modify any files outside the above-mentioned folders
• Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

1. Description of the managed Application and where to find more information
2. Features and capabilities of your Operator and how to use it
3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

• Human-readable name and 1-liner description about your Operator
• Valid category name ¹
• One of the pre-defined capability levels²
• Links to the maintainer, source code and documentation
• Example templates for all Custom Resource Definitions intended to be used
• A quadratic logo

Remember that you can preview your CSV here.

--

¹ If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need

² For more information see here

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runfvdqf
Start Time: 2026-01-26 00:27:53+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2026-01-26 00:27:55+00:00	7 seconds
✔️	acquire-lease	2026-01-26 00:28:07+00:00	5 seconds
✔️	set-github-status-pending	2026-01-26 00:28:15+00:00	7 seconds
✔️	set-github-started-label	2026-01-26 00:28:16+00:00	8 seconds
✔️	set-env	2026-01-26 00:28:28+00:00	7 seconds
✔️	clone-repository	2026-01-26 00:28:39+00:00	a minute
✔️	clone-repository-base	2026-01-26 00:28:39+00:00	a minute
❌	detect-changes	2026-01-26 00:30:22+00:00	51 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/0661f48a4cfece3fac0e5cd92114ef25

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.