Comments (7)
This sounds really interesting. So a given EG server would still target exactly one Kubernetes cluster in which the kernels are launched - these changes simply enable the ability for that cluster to be remote. Is that correct?
You'll also need to take into account the possibility of the user having configured the EG_SHARED_NAMESPACE
functionality. In that case, the remote cluster may not have the enterprise-gateway
namespace and I would argue that we should probably raise an error if remote-k8s-cluster AND eg-shared-namespace are both enabled. The BYO namespace (using KERNEL_NAMESPACE
) should still work, although we should probably ensure that KERNEL_NAMESPACE
does not reflect the EG namespace in which EG resides.
At any rate, those are implementation details that we can work out. We look forward to your pull request.
(Just a note that changes within the Process Proxies functionality, will be dropped in our EG 4.0 release in favor of using the kernel provisioner framework that is now part of the general Jupyter stack, so it would be great if you can participate in the Gateway Provisioners project. I'm (frantically) trying to get things in place for a release over there as we speak. If you're unable to make applicable changes, no worries, we'll port them over at some point closer to making the switch. I just wanted to make you aware of that future transition.)
from enterprise_gateway.
Yes - you opened #1208. 😄
from enterprise_gateway.
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Welcome to the Jupyter community! 🎉
from enterprise_gateway.
So a given EG server would still target exactly one Kubernetes cluster in which the kernels are launched - these changes simply enable the ability for that cluster to be remote. Is that correct?
Yup! That would be exactly correct.
Thanks for reminding me about the shared namespace option! That's something I forgot to consider, I'll also look through the other k8s options to ensure we don't raise a conflict.
In regards to the new gateway provisioners, thanks for making me aware of that as well. I'll take a look there for the effort to port over the new k8s client pattern w remote cluster and let you know.
from enterprise_gateway.
I'll take a look there for the effort to port over the new k8s client pattern w remote cluster and let you know.
You should find things nearly identical with the exception of name changes and the fact that there isn't a hosting application in the repo.
I need to apologize for the existing documentation (still converting from EG), tests (that are nearly zero), and lack of an installable package (hopefully soon), so bear with us.
from enterprise_gateway.
I need to apologize for the existing documentation (still converting from EG), tests (that are nearly zero), and lack of an installable package (hopefully soon), so bear with us.
Is there an issue or PR that tracks the effort to let EG use the Provisioners?
from enterprise_gateway.
So a given EG server would still target exactly one Kubernetes cluster in which the kernels are launched
It would be useful if one could also point to a specific kube context for a given kernel
from enterprise_gateway.
Related Issues (20)
- Only KERNEL_-prefixed envs are flowed to CRD-based kernels
- Publish helm JEG on ArtifactHub HOT 1
- jupyter_client complains on wrogly passed kernel_id to Popen call HOT 1
- Enterprise gateway Spark Operator (Python) kernel fails to systematic restart HOT 3
- Avoid too many retried on kernel shutdown tries HOT 1
- Failed to start kernels (Spark Operator) keeps trying to connect indefinitely
- could not find elyra/enterprise-gateway:3.2.1 HOT 4
- Conda -> Venv for local development HOT 4
- DockerProcessProxy missing abstract method implementation
- Add Karpenter do-not-evict annotations to kernel-pod HOT 2
- Jupyter Enterprise Gateway to also create an Ingress resource along with service for each driver pod to access Spark UI HOT 3
- Add Mutual Authentication Option as a Parameter HOT 3
- Fix doc build HOT 1
- Build fail -> Error response from daemon: No such container: itest-yarn
- Unable to connect kernel HOT 6
- Jupyter lab error starting kernel HOT 8
- Add the option to terminate pending kubernetes kernels if they have events preventing them from starting HOT 4
- KIP cannot use ImagePullSecret when using containerd HOT 2
- kernel Status: Unknown in Jupyterhub 3.2.1 while connecting remote kernel vai Jupyter Enterprise Gateway 3.2.1 on K8s 1.25 AWS EKS HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from enterprise_gateway.