Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #92

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Update README.md #92

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9e8580e
Update README.md
TomAugspurger Aug 20, 2020
8b0bd8a
use frigate
TomAugspurger Aug 20, 2020
842b6e6
restore readme
TomAugspurger Aug 20, 2020
d70df01
restore readme
TomAugspurger Aug 20, 2020
941088e
update gen instructions
TomAugspurger Aug 20, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions dask/.frigate
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,13 @@

This chart will deploy the following:

- 1 x Dask scheduler with port 8786 (scheduler) and 80 (Web UI) exposed on an external LoadBalancer (default)
- 1 x Dask scheduler with the scheduler on port 8786 and the Dashboard on port 80
- 3 x Dask workers that connect to the scheduler
- 1 x Jupyter notebook (optional) with port 80 exposed on an external LoadBalancer (default)
- 1 x Jupyter notebook (optional)
- All using Kubernetes Deployments

> **Tip**: See the [Kubernetes Service Type Docs](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types)
> for the differences between ClusterIP, NodePort, and LoadBalancer.
> for the differences between ClusterIP, NodePort, and LoadBalancer. To access the Dask Cluster from outside of the Kubernetes Cluster (from your laptop, say) you'll neeed to set `scheduler.serviceType` and `jupyter.serviceType` to `LoadBalancer`.

## Installing the Chart

Expand Down Expand Up @@ -191,7 +191,7 @@ If you wish to make a change to the README body you must edit `dask/.frigate` in
To generate the readme run Frigate.

```
frigate gen dask > README.md
frigate gen dask > dask/README.md
```

### Releasing
Expand Down Expand Up @@ -223,4 +223,4 @@ Or manually run the steps below.
{%- endblock %}

{% block credits -%}
{%- endblock %}
{%- endblock %}
8 changes: 4 additions & 4 deletions dask/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,13 @@ Dask

This chart will deploy the following:

- 1 x Dask scheduler with port 8786 (scheduler) and 80 (Web UI) exposed on an external LoadBalancer (default)
- 1 x Dask scheduler with the scheduler on port 8786 and the Dashboard on port 80
- 3 x Dask workers that connect to the scheduler
- 1 x Jupyter notebook (optional) with port 80 exposed on an external LoadBalancer (default)
- 1 x Jupyter notebook (optional)
- All using Kubernetes Deployments

> **Tip**: See the [Kubernetes Service Type Docs](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types)
> for the differences between ClusterIP, NodePort, and LoadBalancer.
> for the differences between ClusterIP, NodePort, and LoadBalancer. To access the Dask Cluster from outside of the Kubernetes Cluster (from your laptop, say) you'll neeed to set `scheduler.serviceType` and `jupyter.serviceType` to `LoadBalancer`.

## Installing the Chart

Expand Down Expand Up @@ -254,7 +254,7 @@ If you wish to make a change to the README body you must edit `dask/.frigate` in
To generate the readme run Frigate.

```
frigate gen dask > README.md
frigate gen dask > dask/README.md
```

### Releasing
Expand Down