earthcube / earthcube/geocodes

NRP Kubernetes Deployment

Open
#56 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

We need to see if we can reimplement the stacks:
* deployment/geocodes-compose-named.yaml
* https://github.com/earthcube/scheduler/blob/dev/dagster/implnets/deployment/compose_project.yaml
* https://github.com/earthcube/scheduler/blob/dev/dagster/implnets/deployment/compose_project_ingest.yaml
an NRP kubernetes deployment implemented for the stack, for a single community.

For dagster, lets use the [NRP postgres](https://nrp.ai/documentation/userdocs/running/postgres/)
For s3, let's use the [NRP Ceph s3](https://nrp.ai/documentation/userdocs/storage/ceph-s3/)

* dagster
* dagster_worflows
* qlever
* Facetsearch and Facetsearch Services
* html proxy like treafik,

We are going to need instructions on a taint, i think.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing deployment/geocodes-compose-named.yaml with the two scheduler compose_project files named in the issue. Review the linked NRP PostgreSQL and Ceph S3 instructions, then define a Kubernetes deployment for the listed Dagster, QLever, Facetsearch, and proxy components serving one community. Done should include deployment instructions and guidance for the required taint.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, kubernetes, postgres
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.