Stop Using CI Scripts to Validate Jupyter Notebooks. Use a Kubernetes Operator Instead.

jupyter nbconvert --execute tells you the notebook ran. It doesn't tell you: Whether it ran with the right GPU, memory limits, or node type Whether the secrets it needs are actually accessible Whether the model endpoint it calls is returning correct predictions Whether cell outputs regressed from last week's golden baseline That gap is why notebooks keep breaking in production despite green CI. The Jupyter Notebook Validator Operator closes it by running validation inside Kubernetes — same environment, same resources, same model endpoints as production. Quick Start # Clone and install CRDs git clone https://github.com/tosin2013/jupyter-notebook-validator-operator.git cd jupyter-notebook-validator-operator make deploy IMG = quay.io/tosin2013/jupyter-notebook-validator-operator:latest # Verify the controller is running kubectl get pods -n jupyter-notebook-validator-operator-system Then submit a validation job: apiVersion : mlops.mlops.dev/v1alpha1 kind : NotebookValidationJob metadata :