List view
- No due date•16/16 issues closed
Milestone owner: @marcelovilla The scope of this milestone is to broaden our security scanning efforts to go beyond infrastructure misconfiguration checks. This includes scanning for vulnerabilities in different dependencies, analyzing container images before they are built, and improving overall CI pipeline coverage using tools like Trivy.
No due date•1/1 issues closedMilestone Owner: @dcmcand This milestone focuses on improving Nebari's cloud storage architecture. The primary issue we're addressing is with the current AWS setup. Conda store storage on AWS is backed by EBS. EBS is only single AZ storage and is write once/Read Once. It is also not resizable by default. All of these represent problems. They mean that if the general node is restarted in a different AZ, then services like conda-store and jupyter-hub cannot start. This effectively turns all deployments on AWS into single AZ deployments which has implications for reliability. It also poses significant problems for PR's that would require replacing or restarting nodes or node groups. Additionally, this means that we cannot scale conda-store workers which has a big impact on scalability. Finally, it means that the general node must be sized to accommodate a conda-store worker that can build large environments. This results in idle Nebari deployments costing much more than they should. The proposed solution is to move from EBS backed storage to EFS backed storage. This would address the above limitations and allow us to move forward with auto scaling. However, there are some concerns about EFS performance for conda-store workloads, so performance will need to be tested once we have a working EFS implementation. After these changes are made, we want to evaluate the storage implementations in GCP and Azure to see if the similarly need to be improved.
No due date•0/3 issues closedUnify core Nebari code and Docker images into one repository, ensuring version alignment and streamlined CI/CD for consistent releases. ## Tasks - Merge the docker-images repository into the main Nebari repo with all CI pipelines disabled; - Update CI/CD to build, test, and tag Docker images alongside Nebari core code. - Update documentation
No due date•0/1 issues closedDefine and collect relevant metrics (e.g., time spent on manual testing if applicable, deployment durations, number of hotfixes) to measure and refine the release process. ## Tasks - Research spike: What available hosting tools would Nebari benefit from that would help with this? - Create a simple logging or analytics mechanism to track release phases and durations. A possible item that was discussed was simple Github actions that take into consideration the actual time between the release tags. - Automate the creation of release checklists/issues at the start of each cycle, capturing all tasks from day one. - Visualize or report data on how long each release step (e.g., candidate build, test, deployment) takes over multiple releases. ## End goal - Release timeline data can be accessed/visualized in our docs; - A documented “release retrospective” after each cycle uses these metrics to gather insights about the weight each code change and stage has over the release
No due dateWe plan to move Dask-gateway to a more accessible and clean implementation relying on Helm and Kustomize instead of direct terraform code. A few things are needed to accomplish this: - Research spike the usage of Dask helm chart for deploying the main service; - Move current components of Dask Gateway in order to use Kustomize; - Make dask deployment optional;
No due date•0/3 issues closedEnsure all test suites (i.e., deployment, integration, and end-to-end) run consistently across local and cloud environments. Standardize testing workflows to achieve parity, improve reliability, and enhance confidence in deployments and releases.
Overdue by 6 month(s)•Due by May 2, 2025•1/7 issues closedMilestone Owner: @dcmcand This milestone focuses on resolving all critical and high-severity security vulnerabilities detected by Trivy in the Nebari codebase. The goal is to enhance the security posture of the project by identifying, prioritizing, and mitigating risks to ensure a more secure deployment.
No due date•1/9 issues closedThe main goal for this Milestone is to identify the current gaps within our release process and suggest possible new alternatives to address or mitigate the identified problems. We aim to achieve a faster, more reliable, and trusted release process. Milestone revisor @viniciusdc
Overdue by 7 month(s)•Due by March 30, 2025•1/2 issues closedMilestone Owner: @viniciusdc
No due date•0/3 issues closedMilestone owner: @marcelovilla This milestone aims to lay the groundwork for an efficient and maintainable strategy for managing Nebari's diverse set of dependencies. This includes auditing current dependencies, identifying pain points, and evaluating tools and processes to keep them up to date with minimal friction and improved security.
Overdue by 4 month(s)•Due by June 30, 2025•0/3 issues closedMilestone owner: @marcelovilla This milestone focuses on collaboratively defining, prioritizing and reviewing the most important user journeys in Nebari. It sets the foundation for improving test coverage by identifying the workflows that matter most to users and maintainers.
Overdue by 5 month(s)•Due by May 30, 2025•0/2 issues closedMilestone Owner: @viniciusdc
No due date•3/8 issues closed