nebari-dev / nebari-dev/nebari-docs
[DOC] - Add node selector label for other cloud providers
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Preliminary Checks
- This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions
Summary
https://www.nebari.dev/docs/explanations/profile-configuration#jupyterlab-profile-node-selectors gives an example for GKE.
And notes that "Other cloud providers will have different node labels."
I want to add node selector labels for other supported platforms.
Flowing labels are known:
- AWS:
dedicated
Steps to Resolve this Issue
- Add a label for AWS
- Add a label for Azure
- Add a label for Digital Ocean
...
### Tasks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the JupyterLab profile node selectors section at the linked documentation page and review its existing GKE example. Verify the node selector labels for each supported cloud provider mentioned in the issue, then update the page with the confirmed labels. Done means the documentation covers AWS, Azure, DigitalOcean, and other supported platforms without leaving provider-specific values unspecified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp, kubernetes
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100