# Bi-weekly Nebari community meeting | 27th Feb 2024 🪴💎

###### tags: community-meeting

**Meeting link: https://meet.google.com/rio-ngrj-kyh**
**Moderator: Chuck**
**Notetaker: Pavithra**

Welcome to the Nebari community meeting!

## Guidelines

* This meeting is covered by [Nebari's Code of Conduct](https://github.com/nebari-dev/governance/blob/main/CODE_OF_CONDUCT.md).
* Please feel free to participate in open discussions, share your projects, or sit back and listen!
* When you'd like to speak in a discussion, use Google Meet's **"raise hand"** feature, and wait for the moderator to call your name.

## Attendees

_All meeting attendees can add your details here!_

* Prefered name / pronouns (optional) / @github-handle / affiliation (optional)
* Rich Signell / he,his / @rsignell / Open Science Computing, LLC
* Marcelo
* Adam
* Chuck
* Michal
* Kim
* Ken
* Johnny
* Pavithra
* Prashant
* Dharhas
* Amit

## Introductions

_If you are new to this meeting, this is the time to introduce yourself!_
_We have an introduction template below, but please share what you're comfortbale sharing. :)_

[Quick intro: Hi, I'm ..! I live in ..., and study ... / work as a ... at .... I'm a Nebari user/contributor/maintianer, and I'm primarily i interested in .... In my spare time, I enjoy ...]

N/A

## Updates and announcements

_Share ongoing work, new releases, something cool you built on Nebari, upcoming conferences, and more!_

* Nebari RC - a few blockers:
* Scaling to zero
* Notebook Jobs
* https://github.com/nebari-dev/nebari/issues/2271

## Discussion topics

_Is there something we should discuss as a group? Something you want feedback on?_
_Note: If you have a usage question, our [Discussion Forum](https://github.com/orgs/nebari-dev/discussions) would be a place to ask. :)_

* [Rich] Deployment of Nebari in more locked-down environments (e.g. NATO). **NATO is currently considering whether to keep trying or abandon Nebari**.
* Major issue was container specification. The NATO deployment has no access to public internet and there are something like 40 containers referenced all over the place. Some changes could be specified in Terraform overrides, but required changing hard-wired locations in Teraform and Python code. So this would have to be done each new version. **Would be a lot easier if there was config option for a custom container registry**.
* The dask dashboard on the Gateway Cluster is still not working because the container URL is not proxied. **Is that fixable on the Nebari side**?
*
> [name=Pavithra Eswaramoorthy] I think this is fixed now

## Actions

_Clear action items with an assignee._

- [x] Add Prashant to the Nebari sync