openshift-quantum-operators icon indicating copy to clipboard operation
openshift-quantum-operators copied to clipboard

Results 6 openshift-quantum-operators issues
Sort by recently updated
recently updated
newest added

### Problem Description Kubernetes has been deprecating API(s), which will be removed and are no longer available in 1.22. Operators projects using [these APIs](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22) versions will **not** work on Kubernetes...

**Describe the bug** Cant access the Qiskit Playground using port-forward of the service **To Reproduce** Steps to reproduce the behavior: I am testing on a kind cluster with `k8s v1.22.1`...

It looks like current implementation does not specify any config parameters https://github.com/qiskit-community/openshift-quantum-operators/blob/master/operators-examples/openshift-qiskit-operator/operator/pkg/apis/singhp11/v1/qiskitplayground_types.go. We need to be able to specify, at least cpu/memory requirements and persistence support

Current implementation seem to keep all user created notebooks on the local cluster. This means that if a pod restarts, all of them will be gone. I think we need...

In this implementation, image is build from scratch. Would it make sense to use on of the "standard" notebook images https://jupyter-docker-stacks.readthedocs.io/en/latest/ for example: FROM jupyter/scipy-notebook # Install Qiskit RUN pip...