Skip to content

Commit 25ece94

Browse files
authored
Merge pull request #498 from asmacdo/local-deploy-explain-domain
Remove `domain` for testing setup
2 parents 53fae55 + a866c45 commit 25ece94

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/docs/how-tos/nebari-local.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,10 @@ The following steps assume you have:
7373
Note You will be prompted to enter values for some of the choices above if they are absent from the command line arguments (for example, project name and domain)
7474
:::
7575

76+
:::note
77+
If you are deploying for testing purposes, omitting the `--domain` option is recommended to prevent issues related to setting up a DNS domain for your deployment. By default, at the end of your deployment, Nebari will return the external IP associated with the Kubernetes cluster's load balancer.
78+
:::
79+
7680
Once `nebari init` is executed, you should then be able to see the following output:
7781

7882
```bash
@@ -124,6 +128,8 @@ If you are a Linux user, you can use the `sudo` command to gain root privileges
124128
sudo echo "172.18.1.100 <domain>" | sudo tee -a /etc/hosts
125129
```
126130

131+
See the [domain-registry documentation](https://www.nebari.dev/docs/how-tos/domain-registry#what-is-a-dns) for details.
132+
127133
:::
128134

129135
### Exposing container network (for MacOS)

0 commit comments

Comments
 (0)