# Bi-weekly Nebari community meeting | 21 May 2024 🪴💎

###### tags: community-meeting

**Meeting link: https://meet.google.com/rio-ngrj-kyh**

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!_

* Tyler Graff
* Chuck McAndrew
* Amit Kumar
* Marcelo Villa
* Kenneth Foster
* Prashant Tiwari
* Adam Lewis
* Michal Krassowski
* Vinicius Cerutti

## 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 ...]

*

## Updates and announcements

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

- Starting next release Cycle this week to test the Jupyter v5

## 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. :)_

* Next release will include the following items:
* Ability to use workload identity on Azure
* Upgrade JupyterHub to 5.x
* Autoscaling of conda-store workers
* Upgrade Prometheus/Grafana stack

The first two items will be included in a first RC to be tested and allow us to give jupyter maintainers feedback on the current beta. Then we will cut another RC to test the remaining updates. Final release will be cut once there's an official release for JupyterHub 5.x.

* Listing over available docker images Nebari current uses:
* Vini: Checking out the helm charts and parsing them would be a good starting point
* Chuck: You can use [this kubectl command](https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container-images/) to grab the current images used accros the running pods;

* Migrating Docker images back to main nebari repository?
* Whay was that changed?
* https://github.com/nebari-dev/nebari/issues/1174
* Discussion points:
* Amit & Chuck: Testing Nebari is currently coupled with big changes made in the docker repository, such as jupyter updates.
* Mike suggested using git modules for easier tracking/syncing with the specified version
* Tyler: Government use cases would like to heavy scans over the files in the docker images:
* Open RFD for the docker migration to single repo or not
* Chuck asked if there would be any preferences considering that? Having those coupled in the same repo might be a better outcome, though it would require testing

* Scanning nebari source code:
* Prashant: Scanning the images as part of the CI, how does it affect user PR considering that feedback loop.
* Chuck: Description on how the static analysis will work with Trivy, we will first address the current vulnerabilities.
* Docs updates, Ken raise some PRs that require review
* Backup & Restore RFD discussion
* Prashant and Chcuck will sync to address next steps
* Removing the main branch in the main repo;
* Bug in Jupyter groups will be addressed as part of the next release cycle discussed above
* Tyler and Ken will submit an RFS to governance to increase maintainer rights

## Actions

_Clear action items with an assignee._

- [ ] Assignee - Action item