azavea / azavea/kubernetes-deployment
Install an Argo workflow to run Dask jobs
- Dominant language
- HCL
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
This is in response to azavea/noaa-hydro-data#120. The task here is to bring the [workflow](https://github.com/azavea/noaa-hydro-data/blob/f79a68d748fcb97a85261fc2bdf5c5f29eb98035/workflows/run-dask-job.yaml) provided in that PR into the cluster as a common piece of infrastructure. It should be available as a `ClusterWorkflowTemplate` in the `daskhub` namespace by default. This implies the need for a flag in `application/daskhub` to select for Argo-related support files, so in the event that Argo has not been installed, the template will be left out.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the referenced run-dask-job.yaml workflow and the application/daskhub configuration. Determine how the workflow can be included as a ClusterWorkflowTemplate in the daskhub namespace by default, and how a flag can omit Argo-related support files when Argo is not installed; done means both selection paths are represented in the deployment resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100