Explore Nebari

[kabilar]

https://www.nebari.dev/

1. See previous discussion in our private Slack thread
2. Let's create a document that explores the user and developer features of Nebari. And compare these features to our AWS DoEKS deployment and 2i2c.
3. Since we have spent a significant effort in updating our deployment of JupyterHub with the AWS DoEKS tech stack, I am hesitant to switch over to another tech stack, but let's explore the strengths of Nebari. And we can then determine if it would be beneficial in the long run to switch to Nebari.

cc @asmacdo @satra @yarikoptic @bendichter

[asmacdo]

IMO the first step should be to set up a deployment on a local kind cluster. https://www.nebari.dev/docs/how-tos/nebari-local

[asmacdo]

I put in a couple hours and ran into a couple issues. Hopefully we get some help on the DNS issue, and I'll resume

2 pods cannot resolve domain nebari-dev/nebari#2555
1 pod Too many open files (solved) nebari-dev/nebari-docs#495