Evaluate Jupyter-apis backend for KF1.7

[mathis-marcotte]

KF1.7 EPIC

The backend will need to be evaluated to make sure of two things:

• that the endpoints we already have in Golang still match logically with the python endpoints from upstream.

• that the endpoints we need for the new features are implemented.
  The main endpoints that we will need to add are the ones needed in the new "Details" pages for notebooks and volumes. On a quick look, there are these GET requests for getting a single resource here for notebooks and here for volumes. But there may be more routes that need to be implemented on our side besides those two.

Will have to make sure to check under the backend folders for "common", "jupyter", and "volumes" in crud-web-apps

[mathis-marcotte]

Looked at the code changes in the backend by comparing 1.7 with 1.6.
The majority of the differences outside of stuff like updated comments are the new requests that will need to be added in our own repo. So here is the list of what we will need to do on our side.

Add from Jupyter component

• GET /api/namespaces/<namespace>/notebooks/<notebook_name>
• GET /api/namespaces/<namespace>/notebooks/<notebook_name>/pod
• GET /api/namespaces/<namespace>/notebooks/<notebook_name>/pod/<pod_name>/logs
• GET /api/namespaces/<namespace>/notebooks/<notebook_name>/events

Add from Volumes Component

• GET /api/namespaces/<namespace>/pvcs/<pvc_name>
• GET /api/namespaces/<namespace>/pvcs/<pvc_name>/pods
• GET /api/namespaces/<namespace>/pvcs/<pvc_name>/events

Modify in volumes component

• GET /api/namespaces/<namespace>/pvcs