Explore possible compatibility issues between Notebook and Enterprise Gateway

[kevin-bates]

This discussion item derives from a conversation started on jupyter/notebook#6251 in this comment. I asked that the discussion and exploration of incompatibility between notebook and EG with respect to asynchronous kernel management be moved here for the time being since it is EG-specific.

cc: @Vishwajeet0510, @rahul26goyal

[kevin-bates]

As per my understanding, from Jupyter Notebook v6.1.0 async kernel management is supported and corresponding changes on JEG side are supported from JEG v2.1.1 onwards.

Ah, ok. First, you should be using async kernel management as soon as possible. Its primary consumers are Jupyter applications that need to frequently spawn kernels - which is EG's exact intent. That said, I understand things can be slow to change at some companies (typically larger).

Async kernel management is optional. In fact, in the current Notebook server release, it's still using synchronous kernel management. Jupyter Server enables Async KM by default, but users could go back to synchronous if they choose - although it's been fairly stable.

I think you should be able to run with EG 2.1.0 against the latest Notebook server - provided your jupyter_client version remains < 7.0.

Are you seeing otherwise?